This repository has been archived by the owner on Jun 26, 2023. It is now read-only.
feat: Add support for typing annotation #90
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
xmnlab
force-pushed
the
add-support-for-type-annotation
branch
from
e124f26 to
50fcb28
Compare
xmnlab
force-pushed
the
add-support-for-type-annotation
branch
4 times, most recently
from
1eeb6af to
329c05f
Compare
xmnlab
force-pushed
the
add-support-for-type-annotation
branch
from
329c05f to
1b980e5
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to add support for an initial typing annotation.
It includes a new operator that will be used for returning type annotation "->"
Also, it performs a bunch of refactoring changes, for example moving camel case format to snake naming convention.
PR Checklist
Ensure that:
build: Changes that affect the build system or external dependencies (example scopes: cmake, meson, etc)ci: Changes to our CI configuration files and scripts (examples: CircleCi, SauceLabs)docs: Documentation only changesperf: A code change that improves performancerefactor: A code change that neither fixes a bug nor adds a featuretest: Adding missing tests or correcting existing testschore:Can be used as a generic task for tasks such as CI, test, support tasks or any other task that is not user facing task.feat:is used for a new feature or when a existent one is improved.fix:is used when a bug is fixed.BREAKING CHANGE:is used when there is a compatibility break.