| Age | Commit message (Collapse) | Author | Lines |
|
|
|
Instead of using the new_ prefix just name them after their type
|
|
As per discussion on IRC. I am about to file an RFC for further
discussion about the more general issue of whether to enforce
invariants through types, typestate, or dynamic checks, but for now,
removing the misleading name "last_unsafe".
|
|
See Issue 1943 for any discussion (reopen it if necessary).
Closes #1943
|
|
This required changing almost all users of hashmaps to import the hashmap interface first.
The `size` member in the hashmap structure was renamed to `count` to work around a name conflict.
|
|
This reverts commit f0250a23d3fa2f8b4a4a4113ca89e41945a4cfed.
|
|
This required changing almost all users of hashmaps to import the hashmap interface first.
The `size` member in the hashmap structure was renamed to `count` to work around a name conflict.
|
|
|