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

Edit: Result coercion no data loss #434

Merged
merged 1 commit into from Apr 30, 2018

Conversation

Projects
None yet
2 participants
@leebyron
Copy link
Collaborator

commented Apr 30, 2018

This edits the "result coercion" section of the scalar types to make it clear that data loss is to be avoided and suggests that internal values of the correct type are the ideal scenario.

Fixes #312

@leebyron leebyron force-pushed the scalar-result-coercion branch from 46b3526 to 6264013 Apr 30, 2018

Edit: Result coercion no data loss
This edits the "result coercion" section of the scalar types to make it clear that data loss is to be avoided and suggests that internal values of the correct type are the ideal scenario.

Fixes #312

@leebyron leebyron force-pushed the scalar-result-coercion branch from 6264013 to 16ef339 Apr 30, 2018

@leebyron leebyron merged commit a4def97 into master Apr 30, 2018

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details

@leebyron leebyron deleted the scalar-result-coercion branch Apr 30, 2018

@lirsacc lirsacc referenced this pull request Jun 29, 2018

Closed

v1 / first release #1

19 of 25 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.