Removed non-empty restriction

[Fili-pk]

I removed non-empty restriction. It is breaking change!

[dzmitry-lahoda]

i guess it may be possible with this support both empty and non empty in same codebase based on proof #30

[Fili-pk]

You are right. I thought this project is dead so i created similar lib that utilizes const checks. https://gitlab.com/fili_pk/bounded-vector

[Fili-pk]

Ok, now it should be non breaking.

[dzmitry-lahoda]

crazy. need to change my pr to this if that works. like if assert does create new type constraint, also being just const assert.

[dzmitry-lahoda]

i tried to do this (as in PR):

struct X<const A: usize>;

impl<const A: usize> X<A> {
    const QWE : () = {
        assert!(A > 0);
        assert!(A != 0);
    };
    pub fn new() -> Self {
        const { assert!(A > 0) };
        const { assert!(A != 0) };
        Self
    }
}

impl X<0> {
    pub fn new() -> Self {    
        Self
    }
}

and got

error[E0592]: duplicate definitions with name `new`
  --> src/bounded_vec.rs:21:5
   |
21 |     pub fn new() -> Self {
   |     ^^^^^^^^^^^^^^^^^^^^ duplicate definitions for `new`
...
29 |     pub fn new() -> Self {    
   |     -------------------- other definition for `new`

My assumption that first and first in both vectors should be named same, but different return parameter.

[Fili-pk]

Const assert it not type constraint. But it gives compiletime error if lib user use it wrongly. For that you need const generic expressions i think.

[dzmitry-lahoda]

So added here empty vs not #31

[dzmitry-lahoda]

@sethdusek i propose to close this in favor of #31