You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When compiling code with @aztec/noir-compiler with the wasm backend it goes ahead and pulls dependencies recursively into a dependency tree. The names of these libraries are then held in a global namespace for the wasm backend to consume.
Because of the global nature of this namespace it can not not distinguish between different versions of the same library (e.g. the name aztec will point to the same library from anywhere in the dependency tree). It currently uses the first version it resolved every time.
We should change the compiler to crash loudly if different versions of the same library are detected at least until the wasm backend supports multiple versions of the same library.
alexghr
changed the title
noir-compiler should fail loudly if incompatible versions of the same library are detected
noir-compiler should fail loudly if two different versions of the same library are detected
Nov 2, 2023
When compiling code with
@aztec/noir-compiler
with the wasm backend it goes ahead and pulls dependencies recursively into a dependency tree. The names of these libraries are then held in a global namespace for the wasm backend to consume.Because of the global nature of this namespace it can not not distinguish between different versions of the same library (e.g. the name
aztec
will point to the same library from anywhere in the dependency tree). It currently uses the first version it resolved every time.We should change the compiler to crash loudly if different versions of the same library are detected at least until the wasm backend supports multiple versions of the same library.
Original discussion: #2737 (comment)
Other discussion here: noir-lang/noir#3213 (comment)
The text was updated successfully, but these errors were encountered: