Closed hackaugusto closed 1 month ago
I split the above into multiple, smaller issues. Some of them may already be worked on, or even fixed on some of the existing PRs.
I wonder if this issue is going to remain relevant once we switch to distributing MAST instead (which I expect to happen shortly after 1277 is merged, as the next in that series of changes):
As part of that switch, the new package format would also be introduced and used in place of MASL libraries. As a result, I'm not sure MASL libraries will even need to exist at that point. So I suppose my question is: do we try to address these issues before that happens, or do we address them in the switch to MAST?
My preference would be to fix this as a part of transition to MAST-based libraries.
Closing this as libraries are now not just parsed but also compiled to MAST.
miden-base
usesMaslLibrary::read_from_dir
to compile the rollup stdlibMaslLibrary
only parses the code withModuleAst::parse
AccountCodeAssemblerError(ReExportedProcModuleNotFound(..., name: ProcedureName { name: "receive_asset" }))
, which is very deceiving.exec
s referencing a module with broken codeAccountCodeAssemblerError(ParamOutOfBounds(1, 0, 0))
, which is the right error but no useful context