When debugging, it would be helpful to have useful type documentation. Especially because Julia uses "naked" imports (unlike Python where you 'import numpy as np' and then 'np.matrixmultiply' (you know what package to look in for the matrixmultiply function)).
My problem:
How can we make it such that when I type?Frame in a jupyter notebook/REPL, I get useful information instead of No documentation found ? Also why are the field names wrong?
If you look at the definition of Frame in Records.jl the fields are entities and n :Records.jl/src/frames.jl
The fact that it tells me it was defined in Records is helpful, but more information would be useful. For example the sentence 'Frame is a wrapper type for Vector and the field n is the length of the field entities.
I also have this complaint of many of the types defined in AutomotiveDrivingModels.jl
Hi,
When debugging, it would be helpful to have useful type documentation. Especially because Julia uses "naked" imports (unlike Python where you 'import numpy as np' and then 'np.matrixmultiply' (you know what package to look in for the matrixmultiply function)).
My problem:
How can we make it such that when I type
?Frame
in a jupyter notebook/REPL, I get useful information instead ofNo documentation found
? Also why are the field names wrong? If you look at the definition of Frame in Records.jl the fields areentities
andn
:Records.jl/src/frames.jlThe fact that it tells me it was defined in Records is helpful, but more information would be useful. For example the sentence 'Frame is a wrapper type for Vector and the field
n
is the length of the fieldentities
.I also have this complaint of many of the types defined in AutomotiveDrivingModels.jl