Further clarify relation to SnoopPrecompile #10
Merged
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
|
Won't this be odd six months from now when no one is using SnoopPrecompile anymore? |
I was also thinking about that, indeed. Maybe people will forget, but on the other hand, maybe people will also end up at SnoopPrecompile via GitHub search and such. Then, not knowing the history could be very confusing. In 1955c8c, I've tried to make the sentences a bit more future-proof. |
|
Seems OK. I guess we can also delete it in a couple of years (maybe just linking to the discourse post). |
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.
I was already wondering why the switch from SnoopPrecompile was necessary. This PR copies the explanation from roflmaostc/DeconvOptim.jl#41.