| 19 Jun 2020 |
|  mathnerd314 joined the room. | 23:10:57 |
| 20 Jun 2020 |
 kiti_nomad | If you have learned powershell, you can pack a copy for windows | 15:24:57 |
| kiti_nomad | Now, many package management tools have appeared on the windows platform, such as choco, scoop, winget | 15:25:58 |
 yorickpeterse | My knowledge of Windows is very limited, so I'd rather leave that to those with more experience :) | 22:53:15 |
| 29 Jun 2020 |
| yorickpeterse | Getting pretty close to the end of type inference/checking | 19:34:27 |
| yorickpeterse | Closures, method calls, and throwing values remain | 19:34:37 |
| yorickpeterse | of course those all happen to be difficult ones, but at least the end is in sight | 19:34:50 |
| yorickpeterse | random example: the Ruby compiler lets you run blocks by sending call to them. But this isn't an actual method though, it just looks like one; defining one for every closure would be too expensive | 19:42:09 |
| yorickpeterse | So now I'm thinking of removing that, in favour of using () (so e.g. callback() opposed to callback.call) | 19:42:45 |
| yorickpeterse | Since Inko is now statically typed, it doesn't need to support dynamic calls to call either, so we can drop the whole idea | 19:43:05 |
| yorickpeterse | downside is that when you look at foo() you don't know if it's a method call, or runs a closure | 19:43:32 |
| yorickpeterse | also downside is that if you do just foo it wouldn't run the closure, so you'd have to use foo(), which is different from methods | 19:46:46 |
| yorickpeterse | * also downside is that if you do just foo it wouldn't run the closure, so you'd have to use foo(), which is different from methods | 19:46:58 |
| yorickpeterse | oh and ugh, we'd have to deal with things like @some_attribute(). I think I will just stick with call for now, but treat it as syntax sugar | 19:51:35 |
| 1 Jul 2020 |
| kiti_nomad | Some simple example functions, you always named foo or bar | 18:56:34 |
| kiti_nomad | Is there any allusion? | 18:56:50 |
| kiti_nomad | In Chinese universities, the textbooks used to learn programming usually name functions as a(), b(), c()... | 18:58:12 |
| kiti_nomad | This led some people to think of learning programming as a math problem | 18:59:23 |
| 2 Jul 2020 |
| yorickpeterse | foo, bar, baz, etc are just commonly used example names; they don't mean anything | 12:57:45 |
| kiti_nomad | I known it | 17:45:37 |
| 5 Jul 2020 |
| kiti_nomad | I wrote a short promotion for inko, the largest IT information platform in China | 15:13:58 |
| yorickpeterse | kiti_nomad: Thanks! :) | 17:57:17 |
| 7 Jul 2020 |
|  @briley899:matrix.org joined the room. | 17:36:17 |
| @briley899:matrix.org left the room. | 22:19:20 |
| 8 Jul 2020 |
|  @alani367:matrix.org joined the room. | 11:25:53 |
| @alani367:matrix.org left the room. | 11:40:06 |
| 13 Jul 2020 |
| yorickpeterse | Spent a week or so re-working parts of the interpreter loop. Specifically, instructions are now fixed-width (16 bytes) and no longer rely on separate heap-allocated vectors for arguments | 19:57:50 |
| yorickpeterse | Prior to this they were 32 bytes, plus the vector space (2 bytes per argument) | 19:58:11 |
| yorickpeterse | Now they are always 16 bytes, with a maximum of 6 arguments | 19:58:17 |
| yorickpeterse | This required a bunch of changes in the compiler so its register allocator is no longer as braindead as it used to be | 19:58:37 |
