Update macro docs #17060
Merged
Update macro docs #17060
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
|
The PCP is mentioned in multiple documentation pages (staging.md, macros-spec.md, macros.md), are all these references incorrect? |
Yes. I will update them. |
nicolasstucki
changed the title
nicolasstucki
force-pushed
the
update-level-checking-nomenclature
branch
5 times, most recently
from
d44833e to
2ebe0ea
Compare
nicolasstucki
changed the title
|
@smarter I completely reworked Mostly I would keep an eye out for latex formatting details that I could have missed. |
nicolasstucki
force-pushed
the
update-level-checking-nomenclature
branch
from
b276a56 to
b6e1950
Compare
Before `3.0` we experimented with the Phase Consistency Principle (PCP) which was described in [A practical unification of multi-stage programming and macros](https://dl.acm.org/doi/10.1145/3278122.3278139). This principle restricted term and types to be used at the same level. Now, and since `3.0` we use a more general version of cross-stage safety where types can be used at any level. Lower levels get erased and higher levels require a given `Type[T]`. The most updated reference is in [Scalable Metaprogramming in Scala 3](https://github.com/nicolasstucki/nicolasstucki/raw/main/Scalable%20Metaprogramming%20in%20Scala%203.pdf). We must remove the use of the term PCP to avoid confusion in the current implementation.
Copy pasted and adapted a bit the contents of chapter 3 of _Scalable Metaprogramming in Scala 3_. The previous version was based on _A practical unification of multi-stage programming and macros_. This version was extremely out of date.
nicolasstucki
force-pushed
the
update-level-checking-nomenclature
branch
from
b6e1950 to
d8c9714
Compare
aherlihy
approved these changes
Mar 16, 2023
Co-authored-by: anna herlihy <herlihyap@gmail.com>
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.
Copy pasted and adapted a bit the contents of chapter 3 of Scalable Metaprogramming in Scala 3.
The previous version was based on A practical unification of multi-stage programming and macros. This version was extremely out of date.
Old nomenclature of cross-stage safty
Before
3.0we experimented with the Phase Consistency Principle (PCP) which was described in A practical unification of multi-stage programming and macros. This principle restricted term and types to be used at the same level.Now, and since
3.0we use a more general version of level consistency where types can be used at any level. Lower levels get erased and higher levels require a givenType[T]. The most updated reference is in Scalable Metaprogramming in Scala 3.We must remove the use of the term PCP to avoid confusion in the current implementation.