[Draft] version 0.5

[Akeit0]

Many API changes.
Pass more tests!

[Akeit0]

@nuskey8
The basic structure is done, but I'd like to see API adjustments, etc.
If you follow the steps from ConsoleApp2, it should be easy to understand for now.

[nuskey8]

I'm currently working on another project, so I'll review it soon.

One thing is that the Lua.CodeAnalysis API has been removed, but I would like to keep it because it's simply useful for analyzing Lua syntax trees.

[marchc1]

As I mentioned in #134; here's a couple other issues I noticed while developing my project. I'm on Nuget version 0.4.2. These are just invalid Lua syntax still compiling issues, though.

• Trailing commas don't throw compile errors
  

• Commas missing after a key = value expression in a table don't cause errors?
  

Sorry if these are already resolved, just wanted to put them on the radar if they aren't (and I can make separate issues for them if they are already resolved, but I didn't want to pollute things with issues already fixed)

[Akeit0]

@marchc1
Both issues have been resolved.
I have completely rewritten the compiler based on implementations of lua and go-lua, so this pre-PR issue is no longer relevant. Of course there may be new issues, but they will be very few.

[Akeit0]

@CodeSmile-0000011110110111

In case this is related, I have been looking for ways to pass arguments to DoString/DoFile. The Lua way is to use load/loadfile apparently but I need to do so from C# and there currently is just no clean way to do so. Should I open a feature issue for this or have I overlooked something?

Currently, we do not have that functionality and will add it in v0.5.
(Edit: use Load(source).Invoke() like something)