Maxime Mangel

Here are some examples code with their compilation equivalent trying to explains my point of view: ## Mapping nullness to `T | null` in JS/TS ```fs type NullableInt = int...

> You're all talking about TS type annotations, right? We are talking about which behavior it should have when targeting JS/TS. The distinction can be/is needed for interop with JavaScript...

Yes, I know that to do we need `string | null | undefinedType` https://github.com/fsharp/fslang-suggestions/issues/538. But IHMO we need to plan for when it will be available, anonymous DUs is planned...

> It's coming who knows when. I know ... > Regardless, we can close the issue then? I don't think we support nullness yet in Fable at least no work...

> Reason is, besides not having to wait for anonymous unions, this would also free Fable from .NET-imposed limitations on the F#9 ` | null` feature, mainly around generic code...

I don't have one under the hand not, and the more the discussion goes and the more compiling to the existing seems to be ok for me. My initial reason...

I think the next step now is to give it a try to compile to: ```ts export type Nullable = T | null | undefined; ``` add some tests to...

When reporting #243, someone pointed me to this PR I tested the behavior of numbered marker in this PR and they are really too big (even bigger than before) 😅...

I am not familiar with the `AsyncIterable` API so I am not sure for what it is used for. But would change the code to be enough? I just added...

I was looking at this issue again and I don't exactly see what your last message was trying to point to. Could you please try to explain what is missing...