sorry, cpu Building [===================================================> ] 151/159: diesel_derives, serde_derive, tower-web-macros, tokio
-
-
Replying to @steveklabnik
I've never looked into it, but I would think that `diesel_derives` should be much cheaper to compile than `diesel` is, since it has much less code (specifically lacking the 8352 line macro invocation saying "implement all of the traits for arbitrary sized tuples").
2 replies 0 retweets 1 like -
Replying to @sgrif @steveklabnik
I did not want to know how that sausage was made. Do you macro that macro somehow?
1 reply 0 retweets 0 likes -
Replying to @jashmatthews @steveklabnik
Yes, all but the first few lines in https://github.com/diesel-rs/diesel/blob/master/diesel/src/macros/tuples.rs … were generated by an editor macro. For a long time we only supported 26 element tuples because my editor macro was just incrementing letters at known indexes and 27 element tuples required `Z` going to `AA`
1 reply 0 retweets 2 likes -
Luckily, that file is likely frozen for eternity (adding to it and moving it around definitely skewed the contribution stats to make it look like I wrote way more code for the project relative to others than I actually did)
1 reply 0 retweets 1 like -
Diesel takes nearly 20 minutes on my 2015 MBP to compile if you enable `128-column-tuples`. I do not know how long it would take with a hypothetical `256-column-tuples` feature, but I do know that the compile time growth is non-linear and it would be greater than 90 mins
1 reply 0 retweets 2 likes
(90 mins is the how long I let it run before I killed the process, the core team agreed we could not add the feature, and we told the person who requested it they should split up their table)
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.