And I won't actually know if it's a good idea until I've fully implemented it.
-
-
-
Replying to @alex_v_bush
Potential change to Diesel. The problem is that it's a big breaking change and I don't know how it'll impact ergonomics
1 reply 0 retweets 2 likes -
Replying to @sgrif @alex_v_bush
Only one way to find out! Nice thing is that you're not 1.0 yet so this kind of stuff is expected.
1 reply 0 retweets 1 like -
Replying to @mgattozzi
You may get a kick out of it actually. https://github.com/diesel-rs/diesel/compare/sg-hlist-spike?expand=1 … -- read the commit messages for deets
1 reply 0 retweets 1 like -
Replying to @sgrif
You're right I did get a kick out of it. I like the idea. Especially if the gains pan out like you want them too!
3 replies 0 retweets 0 likes -
Replying to @mgattozzi
Nobody instinctively guesses "oh I pass a tuple to .order if I want `order by foo, bar`"
1 reply 0 retweets 0 likes -
Replying to @sgrif
I would think a list might be more instinctive. Especially with macros and being more upfront in the docs. .order(hlist![foor,bar])
2 replies 0 retweets 0 likes -
Replying to @mgattozzi
My bigger concern is about `.select(name, hair_color).load::<(String, String)>` than expression position
1 reply 0 retweets 0 likes -
Replying to @sgrif
There's no way to have it implicitly know the type is there? Also getting it into a list format too would be hard I think. Hmmm....
3 replies 0 retweets 0 likes
We could leave just that one top level impl though. We'll see.
-
-
Replying to @sgrif
Hmmm I see now. Either way, it might end up being a good design choice if it works out. Maybe getting people to test it might help.
1 reply 0 retweets 0 likes -
Replying to @mgattozzi
Yes, I will be asking for a lot of feedback on the PR once it's open (if I open it at all)
1 reply 0 retweets 1 like - 5 more replies
New conversation -
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.