rust/src/libsyntax
bors f9fc49c06e auto merge of #17853 : alexcrichton/rust/issue-17718, r=pcwalton
This change is an implementation of [RFC 69][rfc] which adds a third kind of
global to the language, `const`. This global is most similar to what the old
`static` was, and if you're unsure about what to use then you should use a
`const`.

The semantics of these three kinds of globals are:

* A `const` does not represent a memory location, but only a value. Constants
  are translated as rvalues, which means that their values are directly inlined
  at usage location (similar to a #define in C/C++). Constant values are, well,
  constant, and can not be modified. Any "modification" is actually a
  modification to a local value on the stack rather than the actual constant
  itself.

  Almost all values are allowed inside constants, whether they have interior
  mutability or not. There are a few minor restrictions listed in the RFC, but
  they should in general not come up too often.

* A `static` now always represents a memory location (unconditionally). Any
  references to the same `static` are actually a reference to the same memory
  location. Only values whose types ascribe to `Sync` are allowed in a `static`.
  This restriction is in place because many threads may access a `static`
  concurrently. Lifting this restriction (and allowing unsafe access) is a
  future extension not implemented at this time.

* A `static mut` continues to always represent a memory location. All references
  to a `static mut` continue to be `unsafe`.

This is a large breaking change, and many programs will need to be updated
accordingly. A summary of the breaking changes is:

* Statics may no longer be used in patterns. Statics now always represent a
  memory location, which can sometimes be modified. To fix code, repurpose the
  matched-on-`static` to a `const`.

      static FOO: uint = 4;
      match n {
          FOO => { /* ... */ }
          _ => { /* ... */ }
      }

  change this code to:

      const FOO: uint = 4;
      match n {
          FOO => { /* ... */ }
          _ => { /* ... */ }
      }

* Statics may no longer refer to other statics by value. Due to statics being
  able to change at runtime, allowing them to reference one another could
  possibly lead to confusing semantics. If you are in this situation, use a
  constant initializer instead. Note, however, that statics may reference other
  statics by address, however.

* Statics may no longer be used in constant expressions, such as array lengths.
  This is due to the same restrictions as listed above. Use a `const` instead.

[breaking-change]
Closes #17718 

[rfc]: https://github.com/rust-lang/rfcs/pull/246
2014-10-10 00:07:08 +00:00
..
ast_map rustc: Add const globals to the language 2014-10-09 09:44:50 -07:00
diagnostics
ext syntax: Tweak the return value of bytes!() 2014-10-09 09:44:51 -07:00
parse syntax: Convert statics to constants 2014-10-09 09:44:51 -07:00
print syntax: Convert statics to constants 2014-10-09 09:44:51 -07:00
util
abi.rs syntax: Convert statics to constants 2014-10-09 09:44:51 -07:00
ast_util.rs rustc: Add const globals to the language 2014-10-09 09:44:50 -07:00
ast.rs syntax: Convert statics to constants 2014-10-09 09:44:51 -07:00
attr.rs
codemap.rs syntax: Convert statics to constants 2014-10-09 09:44:51 -07:00
config.rs auto merge of #17630 : sfackler/rust/cfg-warnings, r=brson 2014-10-01 09:22:15 +00:00
crateid.rs
diagnostic.rs Use slice syntax instead of slice_to, etc. 2014-10-07 15:49:53 +13:00
feature_gate.rs Put slicing syntax behind a feature gate. 2014-10-07 15:49:53 +13:00
fold.rs rustc: Add const globals to the language 2014-10-09 09:44:50 -07:00
lib.rs Use the same html_root_url for all docs 2014-10-09 10:50:13 -07:00
owned_slice.rs
ptr.rs
show_span.rs
std_inject.rs
test.rs rustc: Add const globals to the language 2014-10-09 09:44:50 -07:00
visit.rs rustc: Add const globals to the language 2014-10-09 09:44:50 -07:00