ijklam
ijklam
> Great that you're looking into this, I'd really love this feature! But keep in mind that these proposals do not yet have an RFC (at least not one that...
> Great that you're looking into this, I'd really love this feature! But keep in mind that these proposals do not yet have an RFC (at least not one that...
By repeat closing and opening the previewer, it may works as expected some time 😂
I do some research on the preview scaling today and find that by utilizing the `clientRenderInfoMessage` we can get a high quality zoomed in picture (as what it is in...
It is same situation for optional parameters. And this only occurs when the method doesn't have overloads. ```fsharp type X () = member _.ID ([] arr) = arr // another...
I see that the [Assert(Boolean, String)](https://learn.microsoft.com/en-us/dotnet/api/system.diagnostics.debug.assert?view=net-8.0#system-diagnostics-debug-assert(system-boolean-system-string)) method is available on all .NET runtime, so maybe this can be implemented without the `CallerArgumentExpression`, just read the source text out, put it...
This feature needs we can correctly recognize ranges with `#line` directives, otherwise it will make it not possible to build the compiler itself. ``` /home/vsts/work/1/s/src/Compiler/pars.fsy(2111,29): error FS0193: internal error: startIndex...
The original line maps introduced from the `nowarn` PR works badly when the compiler is compiling a file with multiple `#line`s for the `CallerArgumentExpression` cases. See this example: ```fsharp #...
`#line` cannot have effect on the caller info `[]` and `[]` now, but in C# and the past F# it does. Maybe this is a break change or regression? F#:...
This PR does not implement "open in types" feature. It needs some refactoring to implement the feature, which needs someone who knows a lot about the typechecking mechanics. I did...