Source tracking interface#1778
Merged
Merged
Conversation
Jupyter uses this, but it should be useful for any kind of IDE, including SLIME.
Bike
force-pushed
the
source-tracking-interface
branch
from
1167551 to
5ff8bbf
Compare
This has worked by coincidence because we are apparently STILL not correctly doing LET bindings in parallel sometimes.
this obviates the need for ext:with-source-location, and gives better source locations to macros besides, since they can get a location for a subform rather than the top level form. The only possible downside would be places that bound *cspi* but did not bind *source-locations*, but that seems like a silly thing to do to begin with.
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
1 participant
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.
So that DEs like Jupyter or SLIME can use Clasp's tracking streams etc. without having to mess with internals.