Andrew Cann

I agree that using quick_error can involve a lot of unnecessary repetition. @tailhook's code above demonstrates this: ``` JsonDecode(error: json::DecoderError) { display("Json decode error: {}", error) description("Json decode error") cause(error)...

Yeah, I wouldn't advocate for `+` or `*` to be implemented on arrays - would it work element-wise? Would the results overflow to the next element (treating the whole array...

Or to put it another way: the bitwise operations aren't really mathematical operations. They're operations on collections of bools of the same shape.

@konsumlamm: Intersection, union and symmetric difference are `&`, `|` and `^` respectively on the bools representing whether an element of the type is included in the set. A more formal...

I'm fine with either `Bytes` or `Vec`, I just think it's odd that I need to use a codec to do this since a UDP socket is already a stream...

That would certainly be a more efficient of way doing it, I see the problem now with just making `UdpSocket` a `Stream` of `Bytes`. Maybe what I *really* want is...

Would it be possible to just merge the "added python 3 support" commit from this PR if it's the other commit which is causing problems? NixOS recently removed python 2...

Oh wow, I didn't notice you'd replied immediately. Thanks! I'm using KVM 3.4 I believe. I just downloaded it off the website today.

`kompile --version` gives me: ``` K-framework version 3.4. Git Revision: 08c9271 Build date: Tue Aug 26 13:56:56 PDT 2014 ```

Similarly, I get compile errors if I define an operator called `=>`. Is there a way to stop the syntax of my language from conflicting with the syntax of the...