There are a lot of optimizations that we plan to add to this path. The intent of this preview was getting a functional version of `dotnet run app.cs` out the door. Items like startup optimization are going to be coming…
There is no timeframe right now. At the moment this is a loose proposal for how to approach union like features in C#. There are a lot more details to dig into here before we'd be ready to move to scheduling and…
The design is not going to allow for struct layout to have memory safety issues when tearing is involved. That is a problem we are very well aware of and consider in designs.
> from the AOT compiler, but none from the C# compiler. The C# compiler has very little knowledge of `[FieldOffset]`. It's expected that developers understand the runtime implications of this.
It's multiple inheritance of behavior, but not of state.
There is a proposal for "sealed enums" on the C# language repo that have the semantics you are looking for. https://github.com/dotnet/csharplang/issues/782
Yeah F# is a bit of a hurdle for contributors. In retrospect if I'd known I'd stick with the project this long I probably would've chosen C#. https://github.com/jaredpar/VsVim/wiki/FAQ#wiki-language
What version are you using? Prior to 1.2 there was a nasty perf bug with :hlsearch that caused it to be sluggish with 1) very large files or 2) a good number of files opened. The bug is mostly fixed in 1.2 but there are…
What version of VsVim are you using? There was a bug with this exact behavior in 1.1 (and possibly 1.1.1). I got it fixed for the 1.2 release which is the current version in the Visual Studio gallery. Bug Details:…
There are a lot of optimizations that we plan to add to this path. The intent of this preview was getting a functional version of `dotnet run app.cs` out the door. Items like startup optimization are going to be coming…
There is no timeframe right now. At the moment this is a loose proposal for how to approach union like features in C#. There are a lot more details to dig into here before we'd be ready to move to scheduling and…
The design is not going to allow for struct layout to have memory safety issues when tearing is involved. That is a problem we are very well aware of and consider in designs.
> from the AOT compiler, but none from the C# compiler. The C# compiler has very little knowledge of `[FieldOffset]`. It's expected that developers understand the runtime implications of this.
It's multiple inheritance of behavior, but not of state.
There is a proposal for "sealed enums" on the C# language repo that have the semantics you are looking for. https://github.com/dotnet/csharplang/issues/782
Yeah F# is a bit of a hurdle for contributors. In retrospect if I'd known I'd stick with the project this long I probably would've chosen C#. https://github.com/jaredpar/VsVim/wiki/FAQ#wiki-language
What version are you using? Prior to 1.2 there was a nasty perf bug with :hlsearch that caused it to be sluggish with 1) very large files or 2) a good number of files opened. The bug is mostly fixed in 1.2 but there are…
What version of VsVim are you using? There was a bug with this exact behavior in 1.1 (and possibly 1.1.1). I got it fixed for the 1.2 release which is the current version in the Visual Studio gallery. Bug Details:…