Introduce a Strong Type for Sparql Variables #400
Closed
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.
Previously, all variables were plain
std::strings
which made them hard to reason about ("does this store a variable, a variable or iri/literal, or does this store an arbitrary string)and easy to make mistakes.
This PR goes one big step in the direction of fixing this, by introducing a
SparqlVariable
type which cannot be implicitlyconverted to and from String.
The next step would be to introduce more of those types, e.g.a
TripleElement
(variable, literal/iri or property path).