Question 1

How do I use parameterized triggers in LiquidState?

Accepted Answer

Set up a parameterized trigger with config.SetTriggerParameter<T> and pass the argument in Fire or FireAsync, as shown in the README examples with string parameters for dynamic state transitions.

Question 2

LiquidState vs Stateless: which is better for .NET?

Accepted Answer

LiquidState excels in performance with zero allocations and efficient graphs, while Stateless is more mature with a larger community. Choose LiquidState for high-performance async needs, Stateless for simplicity and broader adoption.

Question 3

Does LiquidState support hierarchical state machines?

Accepted Answer

No, the README doesn't mention hierarchical states; it focuses on flat state machines, so you'd need to model hierarchies manually or consider alternative libraries.

Question 4

What's the performance benchmark for LiquidState's zero allocations?

Accepted Answer

While not provided in the README, the zero heap allocation claim applies only to synchronous operations, with async incurring standard overhead, so benchmark based on your sync/async mix.

Question 5

How to handle concurrency with LiquidState state machines?

Accepted Answer

Use the built-in machine types like GuardedStateMachine for lock-free protection or QueuedAwaitableStateMachine for ordered async transitions, as detailed in the in-built machines section.

Question 6

Can I use LiquidState with .NET 6 or later?

Accepted Answer

It supports .NETPlatform 1.0, which includes .NETCore, but check NuGet or issues for specific version compatibility, as the library might not be actively updated for newer frameworks.

LiquidState

What is LiquidState?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions