Lily: An interpreted language with a focus on expressiveness and type safety

Post by zaphirplane » Fri, Jul 20, 2018, 11:47 AM UTC

koube wrote: post #10

EwanToo wrote: post #5

Earlier quoted context omitted.

Depending what you want, using go run source.go gives you the compile time checks, while still giving you the source code visibility and simplicity of scripts

I took a look at Go but it seems to be more of a systems language than a scripting language and I assume that means it's less amendable to "This guy across the country needs this information in 2 hours max".

Post by steveklabnik » Fri, Jul 20, 2018, 7:04 PM UTC

bpicolo wrote: post #52

steveklabnik wrote: post #47

Earlier quoted context omitted.

We must look at very different code :)

I actually didn't realize it was doable (not a heavy rust user - just an enthusiast). Kinda hidden away in docs under an example [0] and isn't in the book under hash maps [1]. Might be worth calling out somewhere explicitly? People getting started with rust probably aren't familiar with the trait-based operator overloading system yet. [0] https://doc.rust-lang.org/std/collections/struct.HashMap.htm... [1] https://doc…

Post by falcor84 » Mon, Jul 23, 2018, 9:19 AM UTC

koube wrote: post #16

falcor84 wrote: post #14

Earlier quoted context omitted.

I suppose that print statement was just a silly example, but just in case this may be of use to anyone, note that you can pass multiple arguments to print and they will be printed space-separated, each converted to a str, so you will (practically) never run into type errors. print(str, int)

True, that's a problem I don't have anymore but it's a quick and understandable example of a mistake that I think lots of people had made before. Instead of a comma I would actually recommend f-strings, which are python's string interpolation. The only downside is that the code within the f-strings I think have even less prechecking. https://www.python.org/dev/peps/pep-0498/ Example: print(f"There are {len(lights)} l…