-
Notifications
You must be signed in to change notification settings - Fork 806
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Serialization and deserialization of the typechecking data #18162
Serialization and deserialization of the typechecking data #18162
Conversation
❗ Release notes requiredCaution No release notes found for the changed paths (see table below). Please make sure to add an entry with an informative description of the change as well as link to this pull request, issue and language suggestion if applicable. Release notes for this repository are based on Keep A Changelog format. The following format is recommended for this repository:
If you believe that release notes are not necessary for this PR, please add NO_RELEASE_NOTES label to the pull request. You can open this PR in browser to add release notes: open in github.dev
|
e13c345
to
cb8fa3e
Compare
8ad0442
to
4cc453e
Compare
4cc453e
to
5f0e8a2
Compare
ec6571b
to
2fa7876
Compare
0cdff34
to
3580dd3
Compare
2fa7876
to
219d31d
Compare
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
7710b72
to
1788c19
Compare
8330922
to
9c1e077
Compare
I'll be merging this. There are some very random test failures, don't really understand the pattern there, but cannot repro locally either... will look separately. Otherwise, CheckedImplFile pickling/unpickling seems to more or less work, TcState is coming up! |
043d448
into
dotnet:feature/reuse-typechecking-results
Part of the Stage 2 as per the design doc.