FluNET.Classic 0.1 reflection language foundation - #5
Draft
ppotepa wants to merge 18 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
This PR establishes the first FluNET.Classic 0.1 architecture layer while keeping the Classic surface syntax compatible.
LanguageSnapshotIVerb<TResult>paramsand attributesT(string)fallbacksBoundSentence/BoundPipelineWhy
FluNET.Classic should remain sentence-oriented while allowing the .NET type system itself to describe much of the language. CLR types describe value shape; role interfaces describe semantics; constructors describe binding/cardinality; attributes override conventions; reflection compiles those facts into the language model consumed by parser, binder, tooling and runtime.
Compatibility
The existing
GET/SAVE/FROM/TO/USING/WITH/THEN,[variable]and{reference}concepts remain intact. LegacyIVerb<TWhat,TFrom>now projects into the newer result-only verb metadata model instead of being removed.Validation status
GitHub Actions accepted and queued the new workflow, but GitHub did not allocate a runner (
runner_id: 0), so the job failed before checkout and exposed no build steps/logs. The environment available to this task also cannot resolve github.com for a local clone. For that reason this remains a draft checkpoint and should not be merged until a realdotnet build/dotnet testrun is available.