1483c6d372
FIX: Adjust (mostly remove) inline directives
...
Using the following principles:
- Trivial methods (empty and simple constants) can be inline(always)
- Generic methods don't need any inlining directive at all.
..with the exception of Deref which just seems to be extra important.
- Non-generic items use #[inline] to enable inlining at the
compiler's discretion.
2019-10-09 10:02:20 +02:00
70a9ad67af
DOC: Copyedit the Array doc comment again
2019-09-25 14:48:16 +02:00
babae41d21
DOC: Add safety documentation on Array trait
2019-09-25 14:43:21 +02:00
e86a32d454
MAINT: Port to Rust 2018 edition
2019-09-02 22:07:30 +02:00
f2aad9f9a7
API: Update ArrayExt's methods to expose slices instead of pointers
...
This is a nicer and simpler interface to expose, since the ref to uninit
array to pointer cast is not usable anyway (it's historic now, arrayvec
itself does not use it anymore).
2019-09-01 14:47:44 +02:00
f5290c1eea
FIX: Remove unused .as_mut_ptr() on the Array trait
...
Raw pointer taking should go through the MaybeUninit wrappers around the
arrays anyway, when it is partially uninitialized, which it often is.
The remaining .as_ptr() and .as_slice() methods on Array is only used
on a fully initialized array in ArrayString::from_byte_string
2018-12-16 18:32:14 +01:00
6c099e148f
FIX: Add associated constant for Array's capacity
...
This isn't of much use at the moment, but future Rust features could
mean we can use it.
2018-12-16 18:32:14 +01:00
bf3b8c4f0f
FIX: Unused code warning in array trait
2018-11-30 18:49:28 +01:00
74f86a710e
Merge branch 'master' into master
2018-11-25 10:29:22 +01:00
e355c9eb31
DOC: Hide Array methods on impls
...
These just clutter up the docs. Most important that the users can see
the list of implemented array sizes, not the methods for each of those.
2018-11-25 09:32:29 +01:00
50728e4cda
DOC: Add doc for additional array features flags
2018-11-25 09:24:16 +01:00
f1d73f4feb
FEAT: Add array sizes 33 to 128 and 129 to 255 under feature flags
...
This way we cover all users up to 256 at least. The reason these are not
enabled by default is that they slow down the compilation of the crate
by a factor of 2-3x.
2018-11-25 09:22:51 +01:00
55bedc922a
Make zero-capacity ArrayVec a zero-sized type.
2018-10-14 17:25:45 -04:00
ce009233ae
BUG: Fix 1 << 16 size array impl: only possible on bigger than 16-bit
2017-11-03 19:29:54 +01:00
a2e3fcea3f
DOC: Minor fixes in docs, for ' → ’
2017-10-27 22:54:46 +02:00
2de36ba2ca
Add 65536 to the Array impls
2017-08-06 18:44:48 +02:00
d4bed04908
Add Array implementation for 50, 100 and 200
...
The implementation for 50 would be useful for a use case of mine, if that's alright. 100 and 200 are added for completeness to match 50 existing.
2017-06-14 21:52:38 -07:00
f65ea92da4
Remove the optional generic-array feature
...
- It can be added back later if needed
- A public dependency implies version coupling, and we can't afford to
have it for a niche use case.
2017-03-24 18:57:39 +01:00
da459bcf78
Add constructor ArrayString::from_byte_string(b"abc")
...
This is an alternative constructor that never has capacity errors.
Unfortunately the error case is invalid UTF-8!
2016-12-14 15:01:17 +01:00
60a97632bc
Support generic-array as arrayvec backend
2016-09-28 11:06:20 +02:00
90de29e6cb
Remove zero from the Index trait
2015-09-18 00:53:19 +02:00
be2979d87a
Make sure methods in helper trait Index are inlined
2015-05-23 00:52:26 +02:00
d3b3fc16fb
Implement array sizes in the 16-bit index range
2015-05-22 20:16:41 +02:00
1b42f992ed
Move Array trait to separate file
...
Also remove the ::new() method on the trait
2015-05-22 13:26:01 +02:00
bluss