An implicit require "prelude" gets inserted into the beginning of all crystal programs, and will either load this file, or a different crystal file if the --prelude <new-prelude> build option is provided.
I don’t quite understand what you’re saying, but, i use this hack too add some crack code before run an crystal application. e.g. like following:
crystal run --prelude hacked_prelude "$@"
Assume following is the content of hacked_prelude.cr
require "prelude"
# others code need to run before run app
This feature almost same as the usage of $RUBYOPT ENV for Ruby.
@tsornson Thanks for letting us take part in your exploration.
Your insights are very valuable for guiding developers into understanding how the compiler works.
Maybe we could collect them somewhere more visible? Would you consider writing them down in a form of a blog post or guide?
I’m not sure where to publish it eventually, but maybe the Guides in the Crystal Book could be good place?
Maybe we should do a good plan before suggestion someone take a PR to guides or somewhere in crystal-book, the last similar suggestion from you(the leader of core term) is this post about use zig cc for cross compile, I actively contribute it, but the PR get closed finally, it clearly hurts the enthusiasm for community contributions.
I’m sorry if the experience was disappointing for your. My suggestion here and there is merely to refine the content for publishing in a more visible location because it could be valuable for others. The Crystal book could be a place for that.
In the case you mentioned we eventually agreed that the material is not yet ready for an official guide.
But that shouldn’t mean all effort was for nothing. I’d still encourage you to publish this somewhere in order to make it accessible for readers.
Also FTR, I am a member of the Core Team, but not the lead.
For anyone on the forums not tracking the PR directly, an excellent discussion is happening in it starting from here and down Huge shoutout to @straight-shoota and @ysbaddaden for the feedback so far, thank you!
I’ve mentally debated taking my current rambling / bullet point explorations and writing them out as a story / journey as I dug into the compiler internals, but I’ve also never written a blog post before and not sure I’d trust my word smithing abilities for that Currently where life is for me isn’t great for writing long-form posts like that (work and life are busy), and I’m not sure when that will change.
That being said, maybe even starting in a google doc and seeing where that gets to could be a start. Leave it read-only for anyone wanting to read it, and let me come back if / when life lets me, like a Journal. That could be interesting.
Or terrible. It could also be terrible. Maybe terribly interesting, too. Not mutually exclusive.
Not so quick update, wanted to chime in that I’ve finally ported over all of the changes I had made to the crystal branch of the tool into the source-typer repo itself for version 0.3.0, if anyone wants to try using it directly there :D
Huge shoutout to 
Currently where life is for me isn’t great for writing long-form posts like that (work and life are busy), and I’m not sure when that will change.