Yatao Li
> at what point does it "understand avalonia" binaries? Custom controls, properties etc. that are only visible to XAML after parsing the compiled assembly.
I'm not sure about the details :) But I guess it's somewhat hard-coded -- although it follows the convension (static member NamedProperty vs. property "Named"), the types are different (e.g....
> Alternatively the name could be automatically appended to to give uniqueness. This will be problematic because once the outer type is shadowed, you cannot access it anymore because expression...
@pbiggar well it makes perfect sense to me in that: - "| ... of ..." means named disjunction of multiple types. - "*" means "Cartesian product", not "and" - "and"...
@Happypig375 I imagine `+` to be for C-style tagless unions :) @cartermp see my 1st comment, it breaks existing code that use the same type name over different parameter arity.
I just implemented `fsharp/workspacePeek` and `fsharp/workspaceLoad` support for `coc-fsharp`, and the initialization problem persists. If I disable semantic highlighting: - IncrementalBuild_TypeCheck enumerates all files - Can go to `open module`...
@greatim my poorman's break is always `async{ ... }` without actual async code :p
simply: ```F# async { while true do if foo then return } ```
Uh oh. But why? I _thought_ I understand CE. 😅😅