one.lobster:
import two
foo_a()two.lobster:
namespace foo
def a():
b()
def b():
print "hi"output:
two.lobster(3): error: call to unknown function: b
but yeah, I usually program bottom up, so I may have never encountered these cases
the weirdness is also worse because most errors in Lobster don't happen unless a function is actually called.. so just compiling two.lobster like won't do anything
I have a plan to move a lot of checking from parser -> type checker which likely will fix this, but it is a larger change.
I can look at this one individually tomorrow
My actual use case has them mutually recursive. It can definitely support that without the namespace and just calling
a() from one.lobster. If we add a call to a() to two.lobster and just build two.lobster, it works namespace or no. Namespace + multiple files is the smallest repro I could find
Is there a way to forward declare functions like in C? I can
def b() -> void but that gives me a function type and a different error :P
I'd rather fix it such that forward decl isn't necessary :)
Turns out it was simply using the current namespace, rather than the namespace at the call site, to resolve
b.
I've not yet isolated a reproduction, but have had similar bugs around methods ; ended up having to explicate
this.foo() rather than just foo() because it was incorrectly choosing a different "foo" than the class method ; it was some how provoked by refactoring and moving code around, so apropos of the ball-of-string around order sensitivity
it was getting something like ( from memory ) "no version of foo accepts 3 args" ; the call site was more like
foo(a, b)
because boy does it insert a lot of guard values in debug mode.. it uses 5-10x more stack than in release mode
not perfect yet, but extends what you can do with generics a fair bit
Also, was thinking of moving (or initially just duplicating) Lobster chat to discord.. it seems to have more momentum behind it, with many people already on there.. thoughts?
in particular, gitter's mobile app induces frustration (for me), so I won't miss it ; only the desktop/web app is notable vs its competitors from my pov
Yeah gitter is pretty neat with its instant github integration.. and I'll probably keep it for the foreseeable future.. but Discord seems to be where most people are, and stay. Slack is a bit heavyweight since it requires an account for each group.. that's nice about discord: if you're already on there, it takes no extra effort to hang out in more groups
note: not volunteering :D
just making sure I'm not missing a link
just making sure I'm not missing a link
:)
So for the moment will keep this one and the discord active.. we'll see which is better in the long run
Cool new feature: you can now use explicit generics without having to create a named specialization for structs: aardappel/lobster@bc58e7f
PSA: if you do anything with colors in Lobster I have potentially just broken your stuff with that last commit (the SRGB one). But it its for the best, really. Please read the commit message to learn how to deal with it :) aardappel/lobster@42aca24