Open jariji opened 2 months ago
The syntax is a=Data.Floats()
, not a::Data.Floats()
; i.e. you're assigning/setting a
to use elements from Data.Floats()
. It's not a type assertion, because Data.Floats()
is not a type, and you can reuse properties defined in this way with other generators that produce other element types.
Would "An argument doesn't have a generator assigned!" be better? I'm using exclamation marks here to indicate a critical problem, not to yell (yelling would be "AN ARGUMENT DOESN'T HAVE A GENERATOR ASSIGNED!").
Ideally it would recognize this ::
vs =
syntax mistake specially and tell me. In https://github.com/Seelengrab/Supposition.jl/issues/2 I apparently thought of ::
too so I figure this won't be the last time somebody makes this mistake.
The next best thing might be
argument
a
has noPossibility
assigned. Trya=Data.Just(3)
or similar.
(Maybe giving an example is pushing it too far.) But using the word Possibility
instead of "generator" seems good, since that's what's missing.
As for the !
, we're in an error message so I already know it's a failure: I prefer a calmer experience - just the facts.
What happened?
How could this be communicated better?
It says "An argument doesn't have a generator set!" but
!
)Julia Version
Package Environment