Simonas Kazlauskas

Inability to delegate calls to other FnOnce implementors like this: ``` rust struct A(T); impl FnOnce for A where T: FnOnce { type Output = ::Output; fn call_once(self, args: Args)...

@nrc uncertainty about `Args` being the right thing given the possibility of variadic generics coming along around 2030 is the most major reason this is unstable.

I disagree – the test should be a codegen test _in addition_ to a test that actually verifies that the assumptions hold in practice. There's a good reason why we...

I suspect to support this well alacritty would need to also support smooth scrolling.

Using `servers-file` is about 3 times more efficient compared to the `address` based approach. `addn-hosts` approach, OTOH, is many many more times more efficient than even that. [reference](https://www.reddit.com/r/sysadmin/comments/beqbcj/dnsmasq_is_very_slow_due_to_adblocking/)

It must have been some random Linux, as it was provisioned using ansible IIRC.

[A draft](https://gist.github.com/nagisa/e7185cdd44c2c981c14e) I had written almost a year ago would allow doing bitfields.

Making macro take arguments from the context would make them non-hygienic.

Seems like this would be a non-problem with a portability lint thing. In that case the floating point functions could be cfgd away like atomics are. On Jul 23, 2018...

This RFC does not explain how references to the reference would be handled. That is, the following code must be well formed: ```rust pub fn banana(val: &mut E) -> Option...