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

Draft #3 #2

Merged
merged 14 commits into from Jun 2, 2019
Merged

Draft #3 #2

merged 14 commits into from Jun 2, 2019

Conversation

amirouche
Copy link
Contributor

No description provided.

@amirouche amirouche marked this pull request as ready for review May 5, 2019 16:01
Do not force the use of transactional in primitives to allow
application code to implement its own transaction semantic.
This reverts commit 3f85326.

Actually even if procedures are decorated with transactional, it
doesn't forbid applications to create custom transaction semantic,
because the decorated procedure will accept a transaction object.
It allows to easily extend transaction semantic without having the
wrap the transaction in upper layers.
@arthurgleckler arthurgleckler merged commit 296e9ef into scheme-requests-for-implementation:master Jun 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants