Skip to content

add new compilation options to data sync to OOP.#32726

Merged
heejaechang merged 1 commit intodotnet:masterfrom
heejaechang:addNullableAndMetadataImport
Jan 24, 2019
Merged

add new compilation options to data sync to OOP.#32726
heejaechang merged 1 commit intodotnet:masterfrom
heejaechang:addNullableAndMetadataImport

Conversation

@heejaechang
Copy link
Contributor

2 new options. NullableContextOptions and MetadataImportOptions

if compiler team do this (#12795), IDE side can simply use compiler's serialization rather than doing it in IDE side

fix #31870

2 new options. NullableContextOptions and MetadataImportOptions

if compiler team do this (dotnet#12795), IDE side can simply use compiler's serialization rather than doing it in IDE side
@heejaechang heejaechang requested a review from a team as a code owner January 24, 2019 01:48
@heejaechang
Copy link
Contributor Author

@dotnet/roslyn-ide @jinujoseph @jcouv can you take a look?

@CyrusNajmabadi
Copy link
Contributor

if compiler team do this (#12795),

You probably want to get the compiler team to actually assign this to someone (or just do that work yourself). it's unlikely to get done otherwise. :)

out bool concurrentBuild,
out bool deterministic,
out bool publicSign,
out MetadataImportOptions metadataImportOptions,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was there a reason to add this above the existing values?

Copy link
Contributor Author

@heejaechang heejaechang Jan 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

other values were using default not serialized/deserialized.

@jinujoseph
Copy link
Contributor

@jcouv is this #12795 planned for 16.0 ?
If not we should move this issue+PR to 16.1 as well.

@jcouv
Copy link
Member

jcouv commented Jan 24, 2019

Moved #12795 to "Backlog". Please talk to Jared to schedule.

@jcouv jcouv added the Area-IDE label Jan 24, 2019
@heejaechang
Copy link
Contributor Author

tagging @jinujoseph for approval

@heejaechang
Copy link
Contributor Author

@jinujoseph the API is already in master. so, I think 16.0 should be fine. also, if they change something, it will let them to know that they have to change this as well.

@jinujoseph jinujoseph added this to the 16.0.P3 milestone Jan 24, 2019
@heejaechang heejaechang merged commit 9c6ebde into dotnet:master Jan 24, 2019
var csharpOptions = (CSharpCompilationOptions)options;
writer.WriteValue(csharpOptions.Usings.ToArray());
writer.WriteBoolean(csharpOptions.AllowUnsafe);
writer.WriteByte((byte)csharpOptions.NullableContextOptions);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whenever the serialization format is updated, is there some version number which should be incremented?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

serialization format version number is needed if one is used for persistence. otherwise, version is not needed.

@jcouv
Copy link
Member

jcouv commented Jan 24, 2019

Thanks!

xoofx pushed a commit to stark-lang/stark-roslyn that referenced this pull request Apr 16, 2019
2 new options. NullableContextOptions and MetadataImportOptions

if compiler team do this (dotnet#12795), IDE side can simply use compiler's serialization rather than doing it in IDE side
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FSA reports warnings about nullability needing to be enabled

5 participants