bug: `Libraries` in `masp` format are saved as `masp`s.

[lima-limon-inc]

When storing the core and protocol libraries, these were being stored as masps instead of masl, as described by this comment: https://github.com/0xMiden/miden-vm/blob/eb5d43d82d61f6a18017a8c00e1a3695110b167d/crates/assembly-syntax/src/library/mod.rs#L404-L411.

As an aside, when trying to link these libraries with the compiler, I got the following error:

cargo miden build -L /Users/fabri/Library/Application\ Support/midenup/toolchains/0.14.3/lib -l core.masl

Creating Miden package miden_faucet_mint_tx.masp

failed to deserialize library from '/Users/fabri/Library/Application Support/midenup/toolchains/0.14.3/lib/core.masl': unexpected end of file

[bitwalker]

The issue here is that we're installing .masl artifacts where .masp artifacts are expected, rather than the other way around. Serialization of the Library struct is going away in the next release (most likely), and everything is expected to migrate to packages now that project assembly is implemented. In fact, the build script for the core lib already emits a package file.

[lima-limon-inc]

The issue here is that we're installing .masl artifacts where .masp artifacts are expected, rather than the other way around. Serialization of the Library struct is going away in the next release (most likely), and everything is expected to migrate to packages now that project assembly is implemented. In fact, the build script for the core lib already emits a package file.

Awesome, thanks for the context.