cfallin opened issue #3471:
The discussion around #3420 has made clear that we should, at a minimum, specify which crates we consider to be "internal" and which we consider to be "public" for the purposes of semver compatibility. This issue, to be clear, does not require (for now) any sort of process or stability policy beyond a list of crates; just that we should say "if you use crates X, Y, and Z, then we will follow semver".
I propose that we declare at least the following as such:
cranelift-codegencranelift-frontendcranelift-wasmcranelift-objectcranelift-jitcranelift-native- data structures foundations:
cranelift-entity/cranelift-bforestAny others I've missed?
akirilov-arm labeled issue #3471:
The discussion around #3420 has made clear that we should, at a minimum, specify which crates we consider to be "internal" and which we consider to be "public" for the purposes of semver compatibility. This issue, to be clear, does not require (for now) any sort of process or stability policy beyond a list of crates; just that we should say "if you use crates X, Y, and Z, then we will follow semver".
I propose that we declare at least the following as such:
cranelift-codegencranelift-frontendcranelift-wasmcranelift-objectcranelift-jitcranelift-native- data structures foundations:
cranelift-entity/cranelift-bforestAny others I've missed?
akirilov-arm labeled issue #3471:
The discussion around #3420 has made clear that we should, at a minimum, specify which crates we consider to be "internal" and which we consider to be "public" for the purposes of semver compatibility. This issue, to be clear, does not require (for now) any sort of process or stability policy beyond a list of crates; just that we should say "if you use crates X, Y, and Z, then we will follow semver".
I propose that we declare at least the following as such:
cranelift-codegencranelift-frontendcranelift-wasmcranelift-objectcranelift-jitcranelift-native- data structures foundations:
cranelift-entity/cranelift-bforestAny others I've missed?
Last updated: Dec 06 2025 at 06:05 UTC