Ron Pressler

Yes. The microbenchmark guards a very short-lived in-memory operation, and so irrelevant for the places where `ReentrantLock` is actually helpful for virtual threads. Virtual threads work well with either `ReentrantLock`...

Thanks. What about the font size?

What are the *manual* steps that need to be done in order to package such a library? If I copy the shared libs/dlls to the application directory, what else needs...

The original goal of this method is to prevent races between two threads/machines that may want to create a globally-accessed actor. For your use-case, what's wrong with calling `getActor` first,...

> but maybe the db object would be removed from the db in-between the moment I checked the existence of the actor, the existence of the object and called getOrRegisterActor?...

P.S. > In any event, it is not any more or less transactional than using getOrRegisterActor alone. It may be if the factory would also *create* the DB object.

> I thought the factory was executed as part as the transactional behaviour of getOrRegisterActor, isn't that the case? First of all, that part is not really specified. The only...

> maybe then it could be interesting to include it? That's what locks are made for, and Galaxy will have global locks. Moreover, the factory may in theory be invoked...

What we can do is, instead of recording the bcis instrumented, we record the names of the method calls instrumented. This should be almost as accurate as bcis and far...

There's now a new name-based (rather than bci-based) verification technique 74c2fb42bd8f71fc21e4afd6e2f502f2f3c52550. You can give it a try at `0.7.8-SNAPSHOT`.