Adam Boniecki comments

Results 113 comments of


                                            Adam Boniecki

Default Xamarin templates for Android and iOS are broken in VS

We should either remove these templates or find a way to update them

In FSI, an invalid string literal can break further parsing of string in that interactive session

I think I incidentally stumbled upon a solution as I've been working on lexing recently, so I am looking into this issue. No clue how to unit test this yet...

In FSI, an invalid string literal can break further parsing of string in that interactive session

Reopening as https://github.com/dotnet/fsharp/pull/14182 had to be reverted due to https://github.com/dotnet/fsharp/issues/14757

In FSI, an invalid string literal can break further parsing of string in that interactive session

@MrLuje how are you sending the input to FSI in your example? Because it looks like the input got mangled the third time it was sent. Does not seem to...

In FSI, an invalid string literal can break further parsing of string in that interactive session

Hmm... It does not repro for me at least on the same version of ionide

F# Intellisense is not initialized for net8.0-windows10.0.xxxxx

I unassigned myself - didn't have time to even look into the issue yet :/

Investigate: Special case Lock type in the lock function

Can't do much about this at the moment. Anyone moving to `System.Threading.Lock` now should write their own function to work with it.

Nullness issue - Option.toObj infers input to be an option of a nullable type

@kerams the title says `ofObj`, but you meant `toObj`, correct?

Use Roslyn LSP library instead of Visual Studio

> @vzarytovskii is web tools moving to STJ still scheduled for this sprint? Or did I miss it and it's already gone in? FYI the change has been inserted already

We should disable the --multiemit[+/-] switch in fsi.

We need to make sure disabling this option does not break anyone Vlad says dotnet interactive was using it a year ago