Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add a way to not run the code to create the operation when using the no-op impl. #27

Open
yogurtearl opened this issue Oct 12, 2021 · 0 comments

Comments

@yogurtearl
Copy link
Member

We want to avoid calling thing.slowToString() in release builds.

            busyBee.busyWith(thing.slowToString());
            try {
                thing.process();
            } finally {
                // Espresso will continue
                busyBee.completed(thing.slowToString());
            }

maybe something like:

            // { thing.slowToString() } is only executed when busyBee
            val thingOperationId: OperationId = busyBee.createOperationId { counter -> thing.slowToString(counter) }
            busyBee.busyWith(thingOperationId);
            try {
                thing.process();
            } finally {
                // Espresso will continue
                busyBee.completed(thingOperationId);
            }

sealed class OperationId {
    object NoOp: OperationId()
    class StringOperationId(val operationId: String): OperationId()
}

the noop impl of busybee returns NoOp in release builds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant