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

allow_reentrancy attribute #1783

Closed

Conversation

Artemka374
Copy link

Continuation of work on #1507
which is a part of #1285

.idea/.gitignore Outdated Show resolved Hide resolved
crates/env/src/backend.rs Outdated Show resolved Hide resolved
where
E: Environment,
{
unimplemented!("off-chain environment does not support `reentrance_count`")
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure, that we should implement it in this PR, along with the fact, that we need to expand ExecContext in off-chain engine, so it looks for me as a point for another PR, maybe something like this: #1589

@ascjones
Copy link
Collaborator

Merge master into this PR to fix the CI

@deuszx
Copy link

deuszx commented Aug 17, 2023

What needs to be done here to get it merged? I can help with the coding work.

Copy link
Contributor

@SkymanOne SkymanOne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks quite good for the first iteration. However, I am not fun of renaming set_allow_reentry()

crates/env/src/backend.rs Outdated Show resolved Hide resolved
crates/ink/codegen/src/generator/dispatch.rs Show resolved Hide resolved
crates/ink/codegen/src/generator/dispatch.rs Show resolved Hide resolved
crates/ink/ir/src/ir/item_impl/message.rs Outdated Show resolved Hide resolved
crates/metadata/src/specs.rs Outdated Show resolved Hide resolved
@SkymanOne
Copy link
Contributor

Hey @Artemka374 Any plans on picking this PR up again or should I close it?

@SkymanOne
Copy link
Contributor

Closing due to inactivity

@SkymanOne SkymanOne closed this Dec 21, 2023
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

Successfully merging this pull request may close these issues.

None yet

4 participants