Ary Borenszweig
Ary Borenszweig
@noir-lang/core this is ready to review. Caveat: I made call arguments to unify with coercions. That worked but it also made [one test fail](https://github.com/noir-lang/noir/blob/master/compiler/noirc_frontend/src/tests/name_shadowing.rs) because it's a test that runs...
Ah, it's this entire this: https://github.com/noir-lang/noir/blob/master/compiler/noirc_frontend/src/tests/name_shadowing.rs I think what it's doing is renaming some names to check they produce an error... and I think when that happens a function call...
Ah, yes. I tried adding that code and it wasn't triggering the `add_method` call, until I found this: https://github.com/noir-lang/noir/blob/6109ddc4a12a4f7593c87fcc42a059737febd470/compiler/noirc_frontend/src/elaborator/mod.rs#L1048-L1050 (I read Jake's comment too late 😅)
Also what I did is different from hot code reload. You won't be able to put `debugger`, stop the program, do changes and reload.
@I3oris Of course! Every improvement to the interpreter is very welcome. Plus I find it very fun to work with the interpreter, maybe you too. Oh, and if you want...
> Aren't you trading a process that leaks a GHC, for one you can't kill with Ctrl-C at all? It does get killed. You just get an error message when...
Oh, I don't know about signals either, much less in Haskell. This was just an experiment to see ig I could kill the underlying process no matter how many ctrl+c...
@asterite Sorry for giving no thoughts about this, but a lot of time has passed and I lost context on this, plus I won't have time to look at it......
Hi! Thanks for the reply. This is on Mac osx.