carbon-lang
carbon-lang copied to clipboard
Carbon Language's main repository: documents, design, implementation, and related tools. (NOTE: Carbon Language is experimental; see README)
1. Are we comfortable requiring no mutation of objects with a non-copy-value representation and an active `let` binding? 2. Do we expect our safety story to enforce this at compile...
1. Should we support immutable value semantic bindings nested within variable patterns? 2. Should we retain the `var` statement introducer? 3. Should we add a `ref` statement introducer?
The general intent here is to support basic use of `i32` and similar integer types in min_prelude tests, without all the various arithmetic support. This is in support of #5547...
Similar to the class change made in c6f25e90185f497cfd1cddd5ef87be4aa19238b5 but without tests as it doesn't appear that the same bug is reachable for these cases at the moment - but seems...
When lowering a specific function whose generic was defined in a different file, switch to that other file's `FileContext` and lower the generic there. Also pass the `FileContext` corresponding to...
In preparation for lowering information from multiple `SemIR::File`s into a single `llvm::Module`. The primary purpose of this is to support lowering a local specific for an imported generic function, where...
This proposal introduces the concept of a _form_, which is a generalization of "type" that encompasses all of the information about an expression that's visible to the type system, including...
This avoids reallocating the backing buffer in ValueStore so that references into the ValueStore are never invalidated when adding new values. This works especially well since we never delete values...
This doesn't support actually passing the value of the struct, which is planned to be implemented using thunks. I plan to add more tests in a separate PR. Based on...