Malcom x86

Lisp, it has a lot of resources, and I mean foundational works like SICP.

Haskell is an incremental improvement over functional programming.

Nim is a niche thing, mostly useful to people who know other programming languages.

Assembly is fundamental to the machine, better to learn C first.

I'm a born-again C++ developer, learning it now having not touched it for 20 years. Wow, it's a different beast, and in a good way. Best thing is that my old standby tools still work.

I could repost it, but I have 1 follower, and he is a smug Haskell weenie.

Wouldn't that just be tedious declarations, and not a "port"?

Maybe something SFML related?

Wow, a like from @lefticus.bsky.social aka std::amish

My take:

using using using using using using using using

Translation:

While addicted to type aliasing via the C++ "using" keyword, apply "using" as an example of dependence, utilizing the "using" keyword.

*that uses only one word!

😀

You can pretty much condense the last decade of tech into these two posts

"variables" are just parameters in the enclosing block ;-)

Algol figured out block structure, let's catch up with the definitions.

If you want a POC, get a simple exchange between C++ and Erlang going. Just primitive types (bool would do, initially.)

Benchmark what you have, and gradually introduce concurrency or asynchrony as needed. But not from the start.

Abseil doesn't seem to have Futures, so you're probably mixing Abseil, some other C++ futures implementation, and trying to serialize these things across different runtimes!

This is all a recipe for confusion.

Are you in Erlang-land calling into C++?

If what you're is multiplexing on a connection, Futures are definitely a bad fit for it.

Link to a gist and I will take a look.

P.S. انا كمان اُحِب كربلاء

Wait, how are you communicating _futures_ across two entirely different execution environments!?

What am I missing here? Futures are not "normal" values that can be serialized across different contexts, they're a handle to a value yet to be computed!

I would love to hear more.

a screencast of VS Code + Metals + sbt 1.9.3 used as build server. First, I type in `def foo`, and VS Code shows yellow squiggles indicating a compiler warning. When I hover over, it explains that the procedure syntax is derepcated and that a Quick Fix is available. Selecting the quick fix item fixes the procedure syntax automatically by injecting ": Unit".

released sbt 1.9.3 featuring an improvement on actionable diagnostic (quickfix) support

this is a compiler and tooling level mechanism to send structured fixes long with the compiler warnings. with Metals 1.0.0 and sbt 1.9.3 you can see it in action
https://eed3si9n.com/sbt-1.9.3 #Scala

*Zio, not Zip.

If you're already comfortable with one Effects library (Cats, Zip, etc.) you should be fine.

The book is specifically geared towards those with a Category Theory inclination. Go watch the author's lectures on YouTube first. It's an essential text, but not general.

Java/Kotlin interop is seamless. It has to be, you know, for Android.

But I have only tried up to JDK11, mostly in the Kotlin to Java direction (the inverse can be trickier, not sure.)