Skip to content

Include wasmer-types in workspace with indexmap 2#10

Open
deuszx wants to merge 2 commits intofix-rust-probestackfrom
wasmer-types-indexmap2
Open

Include wasmer-types in workspace with indexmap 2#10
deuszx wants to merge 2 commits intofix-rust-probestackfrom
wasmer-types-indexmap2

Conversation

@deuszx
Copy link
Copy Markdown

@deuszx deuszx commented Mar 10, 2026

  • Uncomment lib/types as workspace member
  • Change wasmer-types workspace dep to path dependency
  • Update lib/types indexmap from 1.6 to workspace (indexmap 2)
  • Update serde feature name from serde-1 to serde (indexmap 2)
  • Remove rkyv indexmap feature (incompatible with indexmap 2)
  • Remove rkyv strict feature (blocks tuple Archive impls)
  • Convert ArchivableModuleInfo IndexMap fields to Vec<(K, V)> with conversion in From impls, since rkyv 0.7 doesn't support indexmap 2 serialization
  • Update rust-toolchain to 1.93.1 (indexmap 2.13 requires 1.82+)

deuszx added 2 commits March 10, 2026 09:57
- Uncomment lib/types as workspace member
- Change wasmer-types workspace dep to path dependency
- Update lib/types indexmap from 1.6 to workspace (indexmap 2)
- Update serde feature name from serde-1 to serde (indexmap 2)
- Remove rkyv indexmap feature (incompatible with indexmap 2)
- Remove rkyv strict feature (blocks tuple Archive impls)
- Convert ArchivableModuleInfo IndexMap fields to Vec<(K, V)>
  with conversion in From impls, since rkyv 0.7 doesn't support
  indexmap 2 serialization
- Update rust-toolchain to 1.93.1 (indexmap 2.13 requires 1.82+)
Both crates had direct indexmap 1.6 dependencies that conflicted
with wasmer-types now using indexmap 2.
@Twey
Copy link
Copy Markdown

Twey commented Mar 10, 2026

What's the reason for this PR? Does the old IndexMap not support the new Rust?

@deuszx
Copy link
Copy Markdown
Author

deuszx commented Mar 10, 2026

There was sth about the indexmap @ 1.6 failing to include the build-std for the custom target (wasm32-web-unknown). The indexmap @ 2.X was already here but it was commented out and the upstream 1.6 was used.

@Twey
Copy link
Copy Markdown

Twey commented Mar 10, 2026

You mean wasm32-unknown-js-web? (Target triples go: architecture-vendor-os-environment.)

@Twey
Copy link
Copy Markdown

Twey commented Mar 10, 2026

I see, this is for linera-io/linera-protocol#5650.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants