Peter Jaszkowiak

This may be a dealbreaker though: Because `Result`, `Option`, tuples, and other built-in types don't implement `PartialEq` like this, tests have to use `.unwrap().1` all over the place because the...

How would you go about writing a generic parser like that without specifying tons of trait bounds all over the place? I tried defining one trait which has all of...

> Did you consider writing a function that converts `YourTree` into `YourTree`? If your parse tree type isn't too large, it shouldn't be too much trouble. I ended up just...

Well I was able to implement a solution that worked for me, but I think this is still a pain point and warrants further study. Also, if the default behavior...

Thanks for looking into it.

It isn't happening for me with `#tick`, it may just be a problem with `#update`. Have you tried `#tick`?

I understand wanting to use as little extra grammar as possible, but I think we should consider using `export` to signify a generic type and for specifying the interface of...

> Adding invalid TS syntax is a no-go for me, it would require every IDE to know of this and people need to get used to that for Svelte only....

Consider the likely performance difference between consecutive and non-consecutive pins in a bus. Say we have 32 pins controlled by a single u32 register, GPIO->DATA_OUT. Where P0 is controlled by...

My main concern is to make it abundantly clear if such a penalty will be required for a given setup. Another confounding factor is that some micros provide a layer...