3 ms·
I don't think anyone is saying never implement an algorithm. There's a time and place. I've seen code bases where these algorithms had ten different implement
by YZF 5y ago
I don't think anyone is saying never implement an algorithm. There's a time and place. I've seen code bases where these algorithms had ten different implementations, some of the with subtle bugs, some of them with some performance issues. Your code will also need to be maintained down the line. There's more to software engineering than writing toposort.
Obviously(?) my Boost proposal was made in jest. Anyways, maybe I'm a little bit jealous that you get to do this all the time ;) I just hope I'm not the one that has to maintain it down the road...
- tubby12345 5y ago>I just hope I'm not the one that has to maintain it down the road... i'm good at what i do - my implementations are clean. they got that way (surprise surprise) as a side-effect of me implementing many times.
- trollytroll69 5y agoevery one says this, yet I've had on multiple occasions debug terrible implementations of lists/stacks. someone's lying