@inr

0 Followers
13 Following
3 Posts
Show threadinrFeb 1
@rsc an aside, but regarding the `bool2` function, is it recognized and handled properly due to the broader context? The reason I ask is that I seem to recall an older Go issue where the compiler will recognize assigning a local variable and returning that, but not this form with a conditional return. And it looks like it is still the case when compiled individually: https://godbolt.org/z/s3dcEfrxf
Compiler Explorer - Go (x86-64 gc 1.25.4)

package p // bool2 converts b to an integer: 1 for true, 0 for false. func bool2(b bool) int { if b { return 1 } return 0 } // I thought this format is required for Go compiler to remove it? func bool2Alt(b bool) (n int) { if b { n = 1 } return }

Show threadinrAug 5, 2023

@robpike This is a great talk. It was the first one I heard by you (I had an interest in array languages) and it's what made me interested in Go, which has since become, probably, my favorite language.

In the array/Go intersection, have you come across this rather unconventional implementation? https://github.com/ktye/i I do not understand it but occasionally browse the source as a curiosity.

GitHub - ktye/i: interpret

interpret. Contribute to ktye/i development by creating an account on GitHub.

GitHub
Show threadinrDec 27, 2022

@neauoire Lovely article, it was the one that got me interested in K.

@bcantrill did an interview with Arthur in the ACM https://queue.acm.org/detail.cfm?id=1531242 containing gems such as

"AW: In C I never learned to use the debugger so I used to never make mistakes, ..."

(And I just love the later retelling of the situation with Bryan's characteristic enthusiasm.)

A Conversation with Arthur Whitney - ACM Queue