@glenathan @sdboyer I built the first usable version of cargo end to end with @carllerche end to end in 3 months and we "finished" in 6.
-
-
Replying to @wycats
@glenathan@sdboyer so not much time to nail even the entire spectrum of known solutions, just the most important.2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@glenathan well, i'm no rustacean yet, but it seems you did a pretty bangup job1 reply 0 retweets 0 likes -
Replying to @sdboyer
@wycats@glenathan which, IMO, is an argument for "big picture" doc's value (be it my article or not) - codesign PM w/lang is goooood1 reply 0 retweets 0 likes -
Replying to @sdboyer
@sdboyer@glenathan I think SAT solvers are a part of the solution, but they miss constraint weighting (when is a "conflict" a conflict?)3 replies 0 retweets 1 like -
Replying to @wycats
@wycats@glenathan i *am* sure there are lots of people out there who think: "boolean satisfiability is understood. whole domain: solved"1 reply 0 retweets 0 likes -
Replying to @sdboyer
@sdboyer@glenathan the decision to allow duplication vs. report a conflict is a weighting decision imo, not a strict one.2 replies 1 retweet 0 likes -
Replying to @wycats
@wycats@sdboyer@glenathan Not sure I understand this, do you think ignoring version constraints on deps is acceptable in some cases?2 replies 0 retweets 0 likes -
Replying to @naderman
@naderman@sdboyer@glenathan no, but duplicating is sometimes (but not always) an acceptable answer.2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@sdboyer@glenathan Ah, I just considered such information input to a dep (potentially SAT) solver1 reply 0 retweets 0 likes
@naderman @sdboyer @glenathan yeah, at some point you're just talking about a general-purpose constraint solver, which I agree could do it.
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.