namark @namark@qoto.org
Joined Jan 2020
@bonifartius if you have the guts, go talk to those people and figure out what's up. Otherwise your "omg I crawled out of my cave and barely heard a voice for the first time in years and I'm scared" alarmist BS doesn't do anything but add fuel to whatever fires might or might not be burning. People lost close friends and family to this pandemic and you are here now wishing and praying "it hits them hard again". "awww it sucks for you, but I hope it happens again so you learn your lesson"(which is what exactly by the way? you tried you failed haha!), what a freaking hero!
PPS: if you want to become one of these fabled rust experts who can allow themselves to write a half baked linked list wannabe - learn modern c++, then learn rust, that's the natural order.
https://dystroy.org/blog/how-not-to-learn-rust/
Mistake 7 : Build lifetime heavy API
Am I reading this right? In rust, a language designed for managing lifetimes, it's prohibitively difficult and inefficient to manage lifetimes.
Solution: freaking copy everything... marvelous...
PS: mistake 3 - linked lists are not hard in rust, they are impossible in safe rust, both to implement and to use properly, and that will always be embarrassing. Even worse when you religiously refuse to admit it, and intentionally miss the whole point of the data structure.
this is roughly what your file format parsing library API should look like
https://en.cppreference.com/w/cpp/algorithm/mismatch
you must tell exactly where you stopped, what was there and, if it wasn't the end, what did you expect instead.
oldern website: need to constantly refresh to update content
modern website: need to constantly refresh cause they hog all the resource
gotta love everyone advertising how header only their libraries are, as if that's some special feature requiring extra effort and not them just being lazy to do proper interface-implementation separation and provide an ABI.
@worldsendless or if you are not a fanboy:
1958: John McCarthy invents a language without syntax designed for teaching grammar and nothing else.
1958 - forever: lisp fanboys go berserk, despite him clarifying numerous times, that the language is no good for high level use and that ones with actual syntax should be used, and continuously rolling in his grave.
every time
Q: why is this undefined behavior?
Everyone: undefined behavior means anything can happen, you cat will explode, your computer will get pregnant, yada yada, omg I love saying this over and over so much, i'm so smart, i know c++! what do you mean why?! standard says so!
No one: *actually explains why undefined, as opposed to unspecified or implementation defined*
another must have flag coming along to accompany -fno-rtti and -fno-ecxeptions, especially on embedded:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p0881r7.html
@bonifartius a can and a bucket is enough to catch one apparently
https://yewtu.be/watch?v=l4PaGvAhV9I
@2ck grinding is not too far from chewing, so if you had trouble with the latter you would probably be doing a lot of the former with a lot of stuff... mixing water with stuff is another remedy for chewing/swallowing troubles... and cooking, once you've accidentally or out of curiosity done it with one thing, you'll try to do it with everything...
strongjaw - chew grain, weakjaw - make dough
borrow checker is basically a whiny garbage collector that screams at you if you make too much work for it
#rust
do i even want to know what you did with intrusive containers? -_-
rust: since you just can't, I made you a nice doubly linked list in std library, yay!
me: yay! I can finally use a list for it's intended purpose - adding/removing elements to/from anywhere without worrying about references to any elements that I don't touch!
rust: uhm... but... but no, you must always worry about references to elements you don't touch, that's how the world works... right?
me: -_- you didn't make a linked list at all did you...
rust: cursor?
me: bye bye generic code, hello edge cases everywhere?
rust: ugh! I thought you just want the terrible memory allocation, isn't that the whole point of this useless thing?
me: no, that's not even... allocators, cmon!
rust: allocators you say?... i've got one!
me: cute...
@saxnot I know it's a different thread and it is broken on my end, there is nothing above the message that you replied to tagging me. Even when I hop over to your instance the conversation seems discontinuous - the reply stars with "yes skills help" while there is no mentions or implications of skill in the post above it, which simply suggest alternative tooling. I ignore all that and reply to the specific post and what it presents. What are you on about?
@saxnot thread seems broken on my end, I blame @jmw150, but anyway, sure, frees their mind, as in instead of studying the problem domain and designing a solution, they have to study the borrow checker implementation and work around it. Did you know you can't write a doubly linked list in safe rust? One has to wonder what other known and unknown entirely safe data structures, that might be the perfect fit for one's use case, one can not write, when one's mind is so free of memory trouble. Oh yes I too love not thinking about essential design elements of the system I'm working on, that's "how big/complex highly multithreaded project with a big dev team" should work, by not thinking. We don't want to have to teach the stupid interns our practices, we just want to unleash a dozen of them on the codebase and while they are wrecking absolute havoc, rely on the tooling to make sure the havoc is not of the particular kind that the latest pop culture buzz is all about. Why are we so careless you might ask, well, because there is no practice to teach, this is how our whole project was built from ground up, and this is how the whole industry works - end users are a commodity ripe for exploitation, quality standards don't exist, pretense and marketing alone sells imaginary products, errors are just a natural phenomenon that nobody is accountable for, THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
@TheAlgorythm @schnedan@kif.rocks @jmw150
