Uncurried external function with @unwrap polymorphic variant argument does not unwrap in output

[illusionalsagacity]

Thank you for filing! Check list:

• Is it a bug? Usage questions should often be asked in the forum instead.
• Concise, focused, friendly issue title & description.
• A minimal, reproducible example.
• OS and browser versions, if relevant.
• Is it already fixed in master?

Using 9.1.3 in the example but also does not compile as expected for 10.0.0-rc.1

example here

[cristianoc]

Not likely to be needed now that we're moving towards uncurried only.

[tatchi]

Is it expected that with rescript 11 (uncurried mode by default), the following code

@module("react-router-dom")
external useNavigate: unit => @unwrap
[
  | #Str(string)
  | #Int(int)
] => unit = "useNavigate"

let navigate = useNavigate()

navigate(#Str("path"))

Gives

[tatchi]

I would have expected the argument to navigate to be unwrapped: navigate("path")

[zth]

Yeah that does look broken. This would be the preferred way to do that in v11:

@unboxed
type stringOrInt = Str(string) | Int(int)

@module("react-router-dom")
external useNavigate: unit => stringOrInt => unit = "useNavigate"

let navigate = useNavigate()

navigate(Str("path"))

[tatchi]

Oh, we can use unboxed with more than one constructor in rescript 11 😁 Cool, thanks 🤗

[zth]

@tatchi yes! 😄 It's quite powerful, and there's a broad range of things you can put in there and still have it be unboxed: https://rescript-lang.org/docs/manual/latest/variant#what-you-can-unbox

However, this still seems to be a breakage introduced by v11. We should either fix it (unlikely) or mention it clearly in the migration guide. Thanks for reporting!