Karl Gaissmaier
Karl Gaissmaier
Hey @incubator4, thanks for implementing this. maybe I just don't understand it, but I don't see that the described function is implemented: "_gohcl.EvalContext constructs an expression evaluation context from a...
Hello @incubator4, i think this is only possible with method values
Hey @incubator4 , sorry for the delay. Maybe I don't understand what you want to show me. Anyway, do you know this blogpost: [build your own DSL with go](https://blog.devgenius.io/build-your-own-dsl-with-go-hcl-602c92ce24c0) and...
maybe you will rethink if you really catch the panic in New() and change the length to 0 under the hood. Perhaps it's generally better to propagate the runtime panics...
hmm, I'm not sure whether this requires a major release. The public interface does not change, only the internal behavior: - the possibility that New() is now panicking (nobody is...
But there are other functions that trigger a panic for the same reason, i.e. if you have specified a `tooBig` start value for `New(tooBig)`, then `New` does not `panic` (and...
and by the way, the current docstring for `New()` does not exclude any `panic`
I no longer use `bitset.New`, but take the zero value `b := &bitset.BitSet{}` and, if I know the maximum length `l`, followed by `b.Set(l).Clear(l)`
@lemire btw, it's up to you to close this issue, no problem for me. Thanks a lot for bitset!