maplant

People told me I "should" exercise for years and I didn't, but when I did I suddenly got a lot less depressed and my life turned around for the better so I'm going to continue to trust other people

Socializing is not a "dull chore" it is a essential component of healthy living[1]

By not socializing, you are avoiding (to quote the linked article) a "fundamental human need." This is not something you can simply live without, just like you cannot live a good live without exercise.

The view you are espousing is fundamentally unhealthy.

[1] https://pmc.ncbi.nlm.nih.gov/articles/PMC11403199/

This is not always possible. Consider the monomorphized output of a generic function. An operation may be dead in one instance but not generally

Idris is bootstrapped on scheme if I recall correctly

I’m not even remotely close to knowledgeable on this subject but I assume metal eating microbes are not possible because metals are not molecular and therefore there’s nothing for them to be broken down into

I get this in every day life, but it comes whenever I have to adjust the pods in my ears. But frankly I kinda expected these to pretty much suck until someone comes out with fully foam tips, at which point my problem will be completely solved as I no longer will have a need to adjust them

But importantly, they’re NOT!

sexpression based hygienic macros

I mean, not to sound rude, but of course it would be someone high up who would make that decision. It’s not like a grunt could decide to scrap a whole new fab

This is the basis for basically every physics engine in some form of another. Collision is divided into the "broad phase" pruning step that typically uses the bounding box of an object and a "narrow phase" collision detection step that uses the more detailed collision primitives

This is called a method based JIT, and is generally the more common approach to JIT compilation. Tracing JIT is a deliberate design choice that is quite different from method based JITs

CPS transforms are not the only way; if you translate the scheme to bytecode for a virtual machine, the call stack and IP can be reified.

But yes, for a compiler specifically, you need a CPS transformation

Thanks! I haven’t really publicized it, my goal is to get it finished first, but I will be presenting on it at the scheme workshop at ICFP/SPLASH

I’m hoping by the end of the year. All of the “difficult” things are finished (control flow, syntax transformers, call/cc, dynamic wind, exceptions, libraries, etc) and it’s just a matter of filling missing base library functions. If there’s something in particular that you need you’re welcome to file and issue or post a message on the discord and I’ll prioritize it.

That being said, Steel is excellent and I highly recommend it if you just need R5RS with syntax transformers

This isn't specific to racket, any implementation of R6RS scheme should fully support this, although the define-syntax form is slightly different.

I checked this with my R6RS implementation and it works just as you would expect (https://github.com/maplant/scheme-rs)

It seems like you've found a very specific situation where tokio's Mutex is helpful but it is simply not common to be structuring an async rust application with a single threaded reactor and copious uses of spawn blocking. The advice to go for the std Mutex first is generally good

If you're using a single threaded reactor you don't need a mutex at all; a Rc<RefCell<_>> will do just fine. And if you want other tasks to yield until you're done holding the borrow, the solution is simple: don't await until you're done. https://docs.rs/tokio/latest/tokio/task/struct.LocalSet.html...

there are absolutely situations where tokio's mutex and rwlock are useful, but the vast majority of the time you shouldn't need them

It sounds like you have a deadlock somewhere in your code and it's unlikely that the choice of Mutex really fixed that

> using a normal std Mutex within an async environment is an antipattern and should not be done

This is simply not true, and the tokio documentation says as much:

"Contrary to popular belief, it is ok and often preferred to use the ordinary Mutex from the standard library in asynchronous code."

https://docs.rs/tokio/latest/tokio/sync/struct.Mutex.html#wh...

It's non-obvious because it completely undermines your point

So there’s no way to gain or lose weight. I see

This is demonstrably false in a lot of cases. For example, if you eat excess calories your metabolism wont adjust. You’ll just get fat.

This is really just my opinion but I always can’t tell when an app uses QT and not positively. QT just looks uglier and feels more windows XP-esque than GTK apps

I could tell instantly in the loading screen because the three blocks in the progress bar move smoothly across it.

care to elaborate on this?

Exercising makes you feel better. It’s a necessary component of living a good life. Extending your life is irrelevant. However, strength training is necessary to ensure the later parts of your life are worth living

It's not an experiment if you're using it in production and it has the capability of destroying production data. That's not experimenting, that's just using the tool without having tested it first.

Pretty stupid experiment if you ask me

Right, these effects seem to lag each other. If prices are affordable, there's no reason to build more housing. We've achieved the goal of making affordable housing. Then, more people move in, prices go up, and the cycle repeats.

Okay, then you'd go from a billion a year to zero. Congratulations.