HAHAHA Good catch!
shaheenery
shaheenery
I haven’t come across them, but I Johnny Winn has brought them up on the Elixir Fountain.
0
electricshaman
I recently watched the Harry Potter movies for the first time and I wondered if it had influenced some of the names. Alchemy, potions, the phoenix, etc.
0
terakilobyte
I thought it was “There are only two hard problems in software development: cache invalidation, naming stuff, and off-by-one errors” 
I suppose Elixir solves that last one for us.
3
OvermindDL1
Nope, this compiles fine. ^.^
Enum.at(something, 4) # something is only 4 in length, so we are one off the end! ^.^
0
Onor.io
I have to thank you for rekindling my interest in looking at OCaml. I had forgotten how much I like the syntax and with an option like Bucklescript I don’t even have to feel guilty about not wrestling with JavaScript. 
1
terakilobyte
True, true. But at least it returns nil, vs something like
int main() {
int test[4] = {1, 2, 3, 4};
printf("%d\n", test[4]); // Yea, though I walk through the valley of the shadow of death
}
0
OvermindDL1
Heh, though using a decent C/C++ compiler that would be caught since you are using constant values and you’d get a warning, where elixir gives nothing. ^.^
Not that elixir is bad at all, most fully typed languages would not get this either without dependent types support (I.E. not Haskell/OCaml/Elm/etc… very few languages have dependent types, although you can emulate them with OCaml’s modules, they are near unrepresentable in Haskell), just it is a folly to consider it a solved problem. ^.^
0
terakilobyte
Agreed. And you are correct, XCode showed a warning on that line of code. Just playing a bit. So far in my Elixir adventures I’ve yet to try to access an item by index. I either filter down or use List.first/1 or List.last/1
0