it's not "native", it's "vanilla"

"native" nowadays means "a system app" -- mobile or desktop, i.e. "does not depend on a web-browser"

what you wanted to say is "vanilla" -- b/c it dosnt need babel, webpack or a WASM compiler

[leonardiwagner]

Thanks, I'm gonna change it.

[ForsakenHarmony]

native for me would also include if it was a language feature, but it's not, more of a hack

[depoulo]

In this spirit, are you specifically trying to align as closely as possible to https://github.com/tc39/proposal-pattern-matching?

[leonardiwagner]

@depoulo No. That proposal is not mature yet, there are a lot of caveats, besides not being able to be close anyway due the proposal features rely mostly on Javascript syntax changes.

Still says "native" on the front-page https://z-pattern-matching.github.io/

It's not native. It's vanilla.

[ForsakenHarmony]

It still says native

[leonardiwagner]

I don't know why this issue was closed, reopening right now, thanks for the warning @ForsakenHarmony and @naomik

Just to remember this project isn't "mine" and it's open to anyone send PRs, I'm currently assigned to update the whole website (including new features done past weeks) which is a higher priority, but after that, I can work on this also if still this description. Thanks.

[ForsakenHarmony]

it's on the website

[leonardiwagner]

as on #52 , we need also to check our main lib dependencies if default parameters is required at all, and place that on new documentation as well (requirements for nodejs, babel, ts, and browser)