Слава Україні! Героям слава!

Same thing with JS/TS, there is limited RTTI cause the base type for all integer types is either `number` (i.e. `float64`) or `bigint`.

@MangelMaxime Please note this is *only* a personal opinion/preference. I have to agree somewhat with @nojaf that if the majority of use cases are for specific language it should be...

IMO it all depends on who we consider the largest audience for Fable. If it's web developers, IMO we shouldn't add more MSBuild properties or ask them to be fiddling...

@MangelMaxime For Rust (much like interop with F# assemblies from C#), it probably makes most sense to build the domain logic in F#/Fable and interface it with a native Rust...

@dbrattli `Seq.toList dict` results in `Coerce` (i.e. `TypeCast`) expr from `Dictionary` to `IEnumerable`, so you should be able to intercept it by inspecting the left and right types in the...

`fable-library-js` seems unused.

@goswinr I don't think it's intentional, it's just that both are implemented with JS arrays, so there is no runtime distinction. We should be able to fix it at compile...

@MangelMaxime Perhaps I'm doing something wrong, but I cannot reproduce with v4.14, with or without `--watch`. ```js import { class_type } from "../fable_modules/fable-library-js.4.14.0/Reflection.js"; import { format } from "../fable_modules/fable-library-js.4.14.0/String.js"; export...

@MangelMaxime Probably different default configurations when using a project file vs a script. In theory an array is mutable so it shouldn't be beta reduced (like other mutables or side...

@leononame Perhaps being a bit more explicit with the generic types can help, something like this: ```fs type Decoder -> 'T module Decode = let ForValue (v: obj) = {...