tx46

> > I edited the initial example. Here's also playground link: > > https://rescript-lang.org/try?version=v12.0.0-rc.2&module=esmodule&code=AIWw9gJgrgNgpgCgETmvAGkglAAjgDwBc4AnAOwEMYcAzARgC4cBnMEOAFQE8AHOOnAF4AfCzadecAExCcSVuwBiUMgGMkAKA2hIsRCl0ZseIqUrUaUphTJhCAC1Lc+AkTgcBLEhGdxZ88QB5B1JlNU0NAHpInFUYD1UAa1owEhAKQhwbCFjHJJwwKEyQnHiyPwAjOBgwAHdtVD1kRqNcAmJyKloAZiYPMg64ZkJ+gHNfV1F+weGx3xlBOQU4MNUAdQ8HAEEAGTAyUdIAOQp2CJ00fRa4TDbTTosAFiZCSfcFuRs7RxJVzSA > > This example looks fine to me when I reformat it. I like to see...

> Even if you were tracking the context, you'd end up with one external taking up multiple lines more often than not because of the hard 100 character limit per...

this is one of my pet peeves with the formatter, i usually just do ``` type t = { // field: bool } ``` when i have a single field...

> > Things like multiline formatting are often just stylistic preferences and should be preserved when they don't break consistency. The same applies to lists and arrays, not just records....

as an added bonus, it's takes multiple formats to make this stable: ``` switch 0 { | 0 // Something something | 1 // Another something => let foo =...

> `bigint` works natively with `@unboxed`: > > ``` > @unboxed > type num = | Float(float) | Int(bigint) > ``` yes, the issue here is that the message from...

i see, is misinterpreted the message i think and thought it should mention bigint as well, but yeah, doing what you just said would make it a tad clearer i...

how do i get it to actually do something? i'm running it from the same dir that rescript.json/package.json is in ``` ❯ npx rescript-tools reanalyze -all -config -debug Warning: can't...

i'm building, but it's not generated. using rescript 12 beta1

``` ❯ npx rescript-tools reanalyze -config -all -debug Scanning lib/bs/src/Main.cmt Source:src/Main.res ``` after `rescript legacy build` the sourcedirs file was generated. but i can't get it to do more than...