ElixirWeekly

Issue #196 - Rewriting Imports to Aliases with Compilation Tracers

Every Thursday: No frills, no click-through, no spam.

Here's what the latest issue looks like:

Logo ElixirWeekly by @elixirstatus Issue #196
Welcome to Issue #196

Apologies. This issue is a day late, because ... stuff is upside-down right now.

Hang in there, stay home, be safe.

This week in Elixir

AyeSQL: Writing Raw SQL
A small tutorial by Alex on how, why and when to use raw SQL.

Rewriting Imports to Aliases with Compilation Tracers
Great post by Wojtek on compilation tracers. The linked import2alias.exs is pretty amazing.

Custom IEx Prompt
You might be bored being locked down and using the same default IEx prompt.

History of Erlang and Elixir
A blog post on how Erlang has morphed into a powerful tool for highly-scalable, concurrent systems over the past decades.

Manipulating INTERVALs in Ecto Fragments
Yevhenii's first blog post ever about how to select entries for last N days/month in Ecto without running into the `invalid_datetime_format` error.

That's it for this round, have a great day!
@rrrene from ElixirWeekly

If you like this newsletter, please tell the world!

You can view this issue in your web browser.

You can subscribe below:

Questions & Answers

Can I submit things I made to be included in the next issue?

Yes! Simply post them to ElixirStatus and you can be sure that they land on my radar.

Is my email address safe with you?

Yes. I'd like to consider myself a trustworthy individual, but then who doesn't?

I am, however, an active member of the open-source Elixir community and the maintainer of Credo and ElixirStatus. I will NOT ruin my reputation by selling your data to a third party.

Why do you require me to confirm my email address?

I just believe that requiring double opt-in to subscribe to any email-based system is a win for both parties: You are safe from unintentionally subscribing and I can be confident that you actually own the email address and want to receive the newsletter I send you :)

Contact

Feedback? Questions? Anything else?

Please contact René Föhring (email or tweet @rrrene for a quick conversation).