Jaap Frolich

Compiler bug in applying an uncurried function when the function has a signature

4

[This](https://rescript-lang.org/try?version=v11.1.0&code=LYewJgrgNgpgBAISgQwFxwN4Cg51gFzmQCdjkBPdACgHJk4BeAPjgCkBnAOg5ADtP8AGjZcAgqQoCAPHSYBKRiw7d2fAVgC+jTDjgwAHvhjFeyKHABWq3uLKUiE8lOU9++FsxEq1hBnABEAKQAlmAwvPjB+OT+ugQOdtpU4QDG4MbCJMQKnlZ8thRUygXknMDIAA7JvGlhxJmkcnKaQA) causes a compile error that the interface doesn't match the signature even though the types are exactly the same in the error. [Without](https://rescript-lang.org/try?version=v11.1.0&code=KYDwLsBOB2CGA2ACAVgZwPbQIKUrAngFyKy4EA8AUqgHTWY1gB8iAvC9XRtI24gEQBSAJYATYNDDCw+fgCh4wMCTL4+ACgkBjdOMgAaFZACUbFmkw48+dZysEaAW1gAHTdB17DpE8blA) the signature it compiles just fine....

@obj attribute regression

7

This caused a bug that one of our tests caught. Is this a known breaking change or a bug? (compare 10.1 vs 11 in the playground) https://rescript-lang.org/try?version=v10.1.2&code=FAguE8AcFMAIDMCWAbaAFATgexhiAhAQwHMQABLAIwCtZoAPUaDAO0OVgFtCBraAMRTpsuAiQBcsABTBYsAH4B9CDEkBnUBkQtiAXgD8AGhBz5yQhoCyWACaIk0G5PjIshUAeOzYAVxaJQLwBKWF0APgQhTBxmMWJQ2AAiRJAAKTUAOldiKW4+QVRo0XAiHKUVaF1EynNEw2kgxqA