mirror of https://github.com/fredrikekre/Runic.jl
You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2.0 KiB
2.0 KiB
TODOs, notes, and various thoughts
TODOs
=and\inshould beinin for loops- Space after
,in tuples, function calls, function definitions,{}etc. - No leading/trailing space in tuples etc
( a, b )->(a, b) - Disallow putting kwargs before all positional args when calling functions
- Space after
;in named tuples, keyword arguments (callsite and definitions) - Indentation
- Trim trailing
;togheter with ws. - Whitespace in ternaries
- Parenteses around expressions in
:operator (e.g.1 + 2:3->(1 + 2):3))
Ideas
- Normalize
1.0e3->1.0e+3? Normalize1.0e+3->1.0e3? Leave alone? I kinda thing it looks clearer with the+and for-it is necessary anyway so that would make it symmetric.
Inconsistencies
-
The
spaces_around_operatorsrule have the following inconsistencies.-
:,^, and::instead fall underno_spaces_around_colon_etc:# current formatting # "consistent" formatting a:b a : b ✖ a^b a ^ b ✖ a::b a :: b ✖ -
<:and<:fall underno_spaces_around_colon_etcif they have no LHS:# current formatting # "consistent" formatting a <: b a <: b ✔ a >: b a >: b ✔ a{c <: b} a{c <: b} ✔ a{c >: b} a{c >: b} ✔ a{<:b} a{<: b} ✖ a{>:b} a{>: b} ✖
-
Bad decisions?
- Space around operators: if there are more, leave alone? This usualy indicate
some kind of manual alignment. Perhaps we can align at
=for connected siblings. - Trimming trailing 0 in floats messes up alignment sometimes.