Qqwy

Qqwy

TypeCheck Core Team

I stumbled across the following curious tidbit of how Elixir’s parser/compiler works:

defmodule Example do
  def {} do
    "Yes, this is allowed!"
  end
end
iex> Example.{}
"Yes, this is allowed!"

I cannot imagine any serious use-case for this, but it is curious.
I believe the cause is that :{} is a special atom that Elixir uses in its AST-definition to describe tuples with more than two elements.

Showing Posts 1 to 3

ityonemo

ityonemo

:rofl: My God, I want to use this for so many bad things that I promise to never make public ever.

henrik

henrik

Not the same, but here’s another fun one: How to "expect(…).to" in Elixir – The Pug Automatic

Qqwy

Qqwy OP

TypeCheck Core Team

It is impossible to import the Example module in this case, however, because that will make Elixir complain that you are attempting to override one of its special forms.

That said, it is possible to wrap any piece of Elixir AST in a macro that alters how the code that is passed to it is expanded. In this way you are able to alter even the behaviour of Elixir’s special forms.
One place where I’ve used this in the past is the Solution library, where the clauses of with and case-statements are overridden to have slightly extended support for tuples.
Another is e.g. the experiment I wrote late yesterday evening which allows bare captures to exist in pipes.


@henrik Thanks for sharing that piece of code! Tuple calls are indeed a strange historic artifact.

— All posts loaded —

Where Next? Top

Trending in Discussions Top

cblavier
Hey there, It’s been more than a year since we started using LiveView as our main UI library and building a whole library of UI componen...
515 12931 101
New
wmnnd
Hey folks, I wanted to share with you a project I’ve been working on for a while: It’s an Open Source (AGPLv3) newsletter tool. Think Ma...
New
raa-ziq
Hi everyone :waving_hand: I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
sntran
In my third year of college, around 2010, I found Erlang. A few years later, I found Elixir. I liked the ideas at once: many small proces...
New
Ganna
Hi everyone, I have 8 years of production experience with Erlang/OTP and I’m just starting to get to know Elixir. What would you learn f...
New
gtcode
I’ve been tinkering with Lynx (by José) via hold_ledger. I used AI to write the code, a separate specification, the tests, and the Lean p...
New
AstonJ
A remark @Garrison made… ..has already inspired a thread for the technical side of reclaiming our internet, but there is of course anot...
New

Other Trending Topics Top

dominicletz
Hey there, I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first. ...
New
mudasobwa
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
KristerV
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
OndrejValenta
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly) AI dream has many faces, but general...
New
kip
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews