Show HN: Mys – an attempt to create a statically typed Python-like language

Post by h8hawk » Mon, Aug 24, 2020, 8:04 PM UTC

eerimoq wrote: post #23

tabtab wrote: post #22

Before making Yet Another Language, I'd like to see a good analysis of the options and trade-offs they offer: what does each design choice make easier and harder. There is probably no free lunch, but maybe we can find a better lunch by balancing things carefully.

For me it's pretty simple. I love Python. I like speed. I like embedded. This is an attempt to take advantage of Python's type hints to create fast and hopefully small binaries that can be executed on embedded devices limited amount of resources (both CPU and RAM). There are probably other languages that would serve the same purpose, but oh well, I can't resist creating another. =)

Post by eerimoq » Mon, Aug 24, 2020, 8:09 PM UTC

h8hawk wrote: post #31

eerimoq wrote: post #23

Earlier quoted context omitted.

For me it's pretty simple. I love Python. I like speed. I like embedded. This is an attempt to take advantage of Python's type hints to create fast and hopefully small binaries that can be executed on embedded devices limited amount of resources (both CPU and RAM). There are probably other languages that would serve the same purpose, but oh well, I can't resist creating another. =)

Have you look at mypyc? https://github.com/python/mypy Its a compiler that support subset of python and mypy's team including Guido work on it. It would be great if this kind of efforts have been done on more realistic project.

Post by striking » Mon, Aug 24, 2020, 8:31 PM UTC

lgeorget wrote: post #32

striking wrote: post #15

Earlier quoted context omitted.

You would be wrong. Try adding a string and number together. That's a type error. Unlike in JS or C, where a lot of these conversions are implicit and only warn if anything. Python determines the types at runtime, but it is very clear about what few operations you're allowed to do on any given set of types.

I wouldn't call C untyped because implicit conversions happen all the times. It's just that it assumes that since you declare your variables with a type, when you assign them, you know what is going to happen.

Post by aidenn0 » Mon, Aug 24, 2020, 9:22 PM UTC

striking wrote: post #15

aidenn0 wrote: post #9

Earlier quoted context omitted.

I would call Python untyped

You would be wrong. Try adding a string and number together. That's a type error. Unlike in JS or C, where a lot of these conversions are implicit and only warn if anything. Python determines the types at runtime, but it is very clear about what few operations you're allowed to do on any given set of types.

    def foo():
      return 1 + "2"

    x = 1
    x = "2"

Post by striking » Mon, Aug 24, 2020, 9:56 PM UTC

aidenn0 wrote: post #37

striking wrote: post #15

Earlier quoted context omitted.

You would be wrong. Try adding a string and number together. That's a type error. Unlike in JS or C, where a lot of these conversions are implicit and only warn if anything. Python determines the types at runtime, but it is very clear about what few operations you're allowed to do on any given set of types.

I can import this with no errors, so Python is untyped: def foo(): return 1 + "2" Another example showing Python is untyped: x = 1 x = "2" x clearly has no type. No variables in python have types.

  >>> 1 + "2"
  Traceback (most recent call last):
    File "", line 1, in 
  TypeError: unsupported operand type(s) for +: 'int' and 'str'