add type safety for environment attribute values #26
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.
Inspired by the #25 PR, this PR increases fixes unknown return values for and increases type safety of attribute values
it is no longer possible to use just any value for
ValuePtr
argument inSQLSetEnvAttr
andSQLGetEnvAttr
, rather only values that can be converted to/fromEnvAttributeValue
newtype can be used. Type safety is increased.SQLGetEnvAttr
can no longer fail silently if driver sets unknown value forValuePtr
as discussed in Unsafe enum usage #12