You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Analysis performs a number of consistency checks that reject malformed justfiles. For example, one check makes sure that all recipe dependencies refer to actual recipes. However, before and after this consistency check, the dependencies field of Recipe is still just a Vec<Name>, so we have no type-level guarantee that the dependency exists, or that the check was performed correctly.
It would be better if the analysis pass transformed the field from a Vec<Name> into a Vec<Rc<Recipe>>, giving us a type-level guarantee that the dependency does in fact refer to a valid recipe.
Todo:
dependencies
aliases
functions
variables
The text was updated successfully, but these errors were encountered:
This is apropros of this post.
Analysis performs a number of consistency checks that reject malformed justfiles. For example, one check makes sure that all recipe dependencies refer to actual recipes. However, before and after this consistency check, the
dependencies
field ofRecipe
is still just aVec<Name>
, so we have no type-level guarantee that the dependency exists, or that the check was performed correctly.It would be better if the analysis pass transformed the field from a
Vec<Name>
into aVec<Rc<Recipe>>
, giving us a type-level guarantee that the dependency does in fact refer to a valid recipe.Todo:
The text was updated successfully, but these errors were encountered: