mirror of
https://github.com/Reuh/candran.git
synced 2025-10-27 17:59:30 +00:00
96 lines
3.6 KiB
Text
96 lines
3.6 KiB
Text
List of potential ideas.
|
|
|
|
To be implemented, theese need to:
|
|
* aesthetically fit into the current Candran/Lua syntax. We can add a few weird glyphs here and there, but our goal *is not* to become a punctuation inventory like MoonScript.
|
|
* vanilla Lua code *must* produce functionaly identical code after going through the Candran compiler, so make sure the additions:
|
|
* are invalid vanilla Lua syntax.
|
|
* are not ambigous with any vanilla Lua syntax.
|
|
* be significantly useful compared to existing Candran/Lua code.
|
|
* be useful without having to rewrite APIs specifically for Candran. Candran intends to make Lua easier, not supersede it.
|
|
|
|
Example currently rejected ideas:
|
|
* Python-style function decorators (implemented in Candran 0.1.0):
|
|
Useless 95% of the time because most Lua APIs applying something to a function are used like applySomething(someArg,func) instead of func=applySomething(someArg)(func).
|
|
This could be adapted, but this will mean unecessary named functions in the environment and it will only works when the decorator returns the functions.
|
|
In this state, these didn't provide anothing useful over short anonymous functions.
|
|
* Whitespace significance.
|
|
Doesn't fit with Lua's verbose keywords.
|
|
|
|
Of course, if you really thinks these would be useful or you found a clever way of making theses work, feel free to open an issue or pull request and discuss.
|
|
|
|
Most of Candran's additions were inspired by MoonScript, CoffeeScript, and Lilia (https://love2d.org/forums/viewtopic.php?f=3&t=82650&sid=b6d9a8dec64afcc1c67806cb5ba65458).
|
|
|
|
Please note that the following ideas are just random though and won't be necessarly implemented, and some won't even work together.
|
|
|
|
Feel free to open issues about ideas you find useful or want to improve. Otherwise, I will only implements them when I really need them or am bored.
|
|
|
|
Actually, open issues for everything. I know of a couple persons using Candran but have no idea what they like and want with it.
|
|
|
|
* class keyword
|
|
class Thing(parents...)
|
|
foo = "bar"
|
|
|
|
new = :()
|
|
stuff()
|
|
end
|
|
end
|
|
local a = new Thing()
|
|
->
|
|
(TODO: define how classes work. May even use ClassCommons)
|
|
|
|
* try / except|catch / finally / else / other keywords
|
|
try
|
|
error("hey")
|
|
catch err
|
|
print(err)
|
|
finally
|
|
clean()
|
|
end
|
|
|
|
* Safe navigation operator
|
|
local name = articles?[0].author?.name (?[] and ?. index opeators)
|
|
or
|
|
local zip = lottery.drawWinner?().address?.zipcode (expr? existence test suffix)
|
|
|
|
See http://coffeescript.org/#existential-operator
|
|
|
|
* static type checking
|
|
local a = externalFunc() -- unknown
|
|
if a == "hey" then
|
|
-- a = string
|
|
a:sub(5,3) -- ok
|
|
a:exit() -- error!
|
|
else
|
|
-- a = unknown
|
|
a:exit() -- ok
|
|
end
|
|
|
|
Will need to define stuff for a lot of Lua libraries (see the work already done by TypedLua).
|
|
|
|
While we're talking about static analysis, what about forking luacheck into candrancheck? Or at least make the line mapping work.
|
|
|
|
* array slicing
|
|
local b = a[3:5:1]
|
|
|
|
* Destructuring assignment
|
|
local pos = { x = 5, y = 12 }
|
|
|
|
local {x, y} = pos -- x, y = pos.x, pos.y
|
|
local {a, b, x = x, y = y} = pos -- x, y = pos.x, pos.y, a = pos[1], b = pos[2]
|
|
local {a, b, :x, :y} = pos -- shorthand for the above line. Or .x, .y
|
|
local {:x.u} = pos OR {:x:u} OR {.x.u} -- u = pos.x.u
|
|
local [x, y] = pos -- x, y = pos[0], pos[1]
|
|
local x, y $= pos
|
|
|
|
And in implicit assignments:
|
|
for i, {x, y} in ipairs(positions) do
|
|
|
|
* String interpolation
|
|
Delimited by ``:
|
|
`Hi, my name is ${@name}` -- -> "blaba" .. tostring(@name)
|
|
Also allows multi-line with this maybe?
|
|
|
|
* Other potential inspiration
|
|
https://www.ruby-lang.org/fr/
|
|
|
|
Well done, you're at the end of the file!
|