📝 Group and Sort Data in Latte Templates Like a Pro
In the latest update of Latte, we are introducing several significant enhancements that will simplify and make more efficient the work with data in your templates.
#TodayInHistory 1984 - Ashton-Tate introduces the dBase III relational #database program for IBM PC-compatible computers.
dBase was one of the first database management systems for microcomputers and the most successful in its day. The dBase system included the core database engine, a query system, a forms engine, and a #programming language that tied all of these components together.
A clean Git history is the key to successful teamwork and quick bug fixes. Errors can only be successfully tracked down if it is always possible to trace when and where code was changed by whom and for what reason.
🥴 However, in the rush of the battle, the changes that are packaged in a commit are sometimes not taken very seriously. Who has never experienced this? A change that is actually unrelated to the current work package has made it into the commit because the file has already been saved temporarily.
💡The solution: With an "interactive add" (git add -i), you can pack partial changes ("hunks") into a commit and specify line by line what should be included in the next commit.
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.