Sanjiva Weerawarana

We have discussed doing this same thing for HTTP services as well.

We already have `bal pull module` .. shall we just make `bal pull` (without a module name) to mean pull deps?

Big +1 for enforcing the proposed behavior. Which means if the file is there we shouldn't update it and try to build per that file. If that file is out...

It seems to me this is logically incorrect: ```T t = check expr-returning-T-or-error on fail e => expr-of-type-error``` because `check` is supposed to remove the error. Would this work? ```T...

Ack .. that works. I was trying to avoid using the expression function syntax. But it solves the need!

I'm +1 for going ahead with @sameerajayasoma proposal above. I don't see any major negative comments above .. if there is can someone restate it please? We can also introduce...

So there's one more constraint: * None of the subdirs in generated can have the same name as subdir of modules/ I'm a bit uncomfortable with the idea of merging...

Yeah I don't think we need to change the design dramatically to do this. If we can add an annotation or a keyword to change storage model, and we add...

Another more first class way to solve this would be to add a concept of a "data" variable: ```data string s = ("some string" | ?);``` And then use a...

How about ``` @embed {pattern: "x.text"} const string data = ?; ``` This is declaring a constant and saying the value is coming from somewhere else. The static annotation tells...