All this time I've been using the return value of snprintf as the number of characters actually written, when it's in fact the number of characters that would be written if the max size passed in were large enough.
In fact: "If the resulting string would be longer than n-1 characters, the remaining characters are discarded and not stored, but counted for the value returned by the function."
usually, it is used to define methods, but in function arguments, it serves as syntactic sugar so you don't have to name generic types... but in a return type, it has a meaning that is slightly different, and actually expresses a semantic not even vanilla haskell can represent!
basically, instead of being able to return any type implementing a trait, it states that it can return at least one type that implements a trait.
in haskell terminology, specifying a generic type parameter is "forall a", while returning an "impl" is "exists a".
Sometimes when tweaking things that are very sensitive, such as audio generation or physics systems, I just play around with parameters for a while, sometimes getting cool results, sometimes screwing up, quickly saving and testing as I go.
Then I feel like going back to something I had earlier, but it's hard to reproduce it. I don't have a great solution for that yet, maybe I should just have a mode where I commit every save to git or something?
Does anyone else do that?
Discover essential techniques to check for column existence in R data frames!
Use %in% with names() or colnames(), explore dynamic checks with exists() and within(), or identify patterns with grepl(). Experiment with these methods in your projects.
I'm working on a #programming project (#opensource) and I want to make a post about it on #HackerNews.
It is functional and works quite well for having started work on it recently. Should I just make the post on HN?
Is it not possible to use grave accents in rust proc-macros? When I do, I get an "unknown start of token" error, even though it /is/ the whole token. When taking a peek at the TokenStream given to the proc-macro function, the grave doesn't appear at all
“To use for await item in streamOfItems {...}, you need an AsyncStream. It is very common that you already have an existing Combine publisher, and you want to use the nice Swift Concurrency syntax.”
This tool is used to spoof DHCP servers. It sends fake DHCP offers to a specific network interface and manipulates the IP addresses of network devices.
If you are an unemployed software dev in the states, this directly affects you. Greedy corps aim to permanently undercut prospects of today's countless unemployed devs (experienced and new) by promoting a false narrative of a "labor shortage." Take a look and please consider leaving a comment within the remaining 2 days. If this passes, you can kiss your job prospects goodbye. https://www.reddit.com/r/cscareerquestions/comments/1cogset/amidst_mass_layoffs_the_us_department_of_labor_is/
Preview of what I have been working on recently. The core of this crate is a mere two traits. The crate will ship with a number of parsers and combinators, none of which rely on anything not exposed to downstream users.
I've attached a real-world situation, taken verbatim from the test suite. Parsing integers isn't as efficient as it could be yet, as it's using a naïve method.
Parsing in general compiles to be extremely efficient, and using it is ergonomic.
My main focus for my Master's in Computer Science has been on Rust, but I'm always looking to expand my skillset. That's why I'm excited to dive into the Golang Programming bundle by hashtag #Packt on Humble Bundle. This bundle offers a great opportunity to learn Golang, a powerful open-source language gaining traction in the tech industry. I'm particularly interested in the "Go Programming - Beginner to Professional" book, which seems like a perfect starting point for anyone new to Go, like myself.
Is anyone else exploring Golang?
Feel free to share your experiences or learning resources in the comments below!
Guys I need some helping hand. I need some good reading (book/article) on the proper way of writing OOP. I gave a project where we use classes, but they are more used as a package if functions then working like objects. Like a class of only statics, passing around IDs not the real objects of data (this sending SRP down the drain), arrays, generally functional programming with extra steps. I'd fancy even a discussion as I want to slowly explain all that to my teammates #php#oop#programming
TIA