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.

Sign up for GitHub

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

Jump to bottom

[Feature]: Improvements for koba #159

Open
1 task done
qalisander opened this issue Jun 25, 2024 · 2 comments
Open
1 task done

[Feature]: Improvements for koba #159

qalisander opened this issue Jun 25, 2024 · 2 comments
Labels
effort: high Large or difficult task. needs information We need more information to work on this. priority: 1 We will do our best to deal with this. type: feature New feature request. uphill Some research/design is needed before this can be implemented.

Comments

@qalisander
Copy link
Member

What is the feature you would like to see?

I think we shouldn't leave koba as it is and explore area of improvements:

  • think how to store constructor logic next to contract logic and field declarations, e.g inside sol_storage! macro
  • think how to spread constructor logic among inherited contracts and implementation, e.g. user of pausable shouldn't know how to instantiate it

Contribution Guidelines

  • I agree to follow this project's Contribution Guidelines
@qalisander qalisander added type: feature New feature request. needs triage Needs to be assigned the appropriate labels labels Jun 25, 2024
@alexfertel alexfertel added priority: 1 We will do our best to deal with this. needs information We need more information to work on this. effort: high Large or difficult task. uphill Some research/design is needed before this can be implemented. and removed needs triage Needs to be assigned the appropriate labels labels Jun 25, 2024
@alexfertel
Copy link
Contributor

This one as well #145

@alexfertel
Copy link
Contributor

This one too #128

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
effort: high Large or difficult task. needs information We need more information to work on this. priority: 1 We will do our best to deal with this. type: feature New feature request. uphill Some research/design is needed before this can be implemented.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alexfertel @qalisander