Rearrange the API again to fix compilation environments #9
Conversation
This file contains 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
Bike
force-pushed
the
compiler-environment-redo
branch
from
6250037
to
134c411
Compare
A lot to summarize, but basically: 1) Any environment can inherit from another environment. The functions in Clostrum check for inherited data. The functions in clostrum-sys do not have to, so implementations can focus on themselves, as long as they provide a PARENT somehow. 2) FUNCTION-DESCRIPTION etc. accessors are eliminated. Instead, compilation and runtime environments are accessed through a common API. The only real differences between them are that a) run-time-environments can't inherit from compilation envs b) compilation environments do not have function or variable cells c) or packages 3) said common API includes new OPERATOR-FTYPE etc. accessors. TODO: Tests, documentation.
Bike
force-pushed
the
compiler-environment-redo
branch
from
134c411
to
25d17e7
Compare
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.
A lot to summarize, but basically:
functions in Clostrum check for inherited data. The functions
in clostrum-sys do not have to, so implementations can focus
on themselves, as long as they provide a PARENT somehow.
compilation and runtime environments are accessed through a
common API. The only real differences between them are that
a) run-time-environments can't inherit from compilation envs
b) compilation environments do not have function or variable cells
c) or packages
TODO: Tests, documentation.
See precipitating discussion in #sicl: https://irclog.tymoon.eu/libera/%23sicl?around=1697887992#1697887992