Skip to content
BranchesTags

Repository files navigation

Elixir logo

CIOpenSSF Best Practices

Elixir is a dynamic, functional language designed for building scalable and maintainable applications.

For more about Elixir, installation and documentation, check Elixir's website.

Policies

New releases are announced in the announcement mailing list. You can subscribe by sending an email to elixir-lang-ann+subscribe@googlegroups.com and replying to the confirmation email.

All security releases will be tagged with [security]. For more information, please read our Security Policy.

All interactions in our official communication channels follow our Code of Conduct.

All contributions are required to conform to our Open Source Policy.

Bug reports

For reporting bugs, visit our issue tracker and follow the steps for reporting a new issue. Please disclose security vulnerabilities privately in our Security page.

All currently open bugs related to Elixir are listed in the issues tracker. The Elixir team uses the issues tracker to focus on actionable items, including planned enhancements in the short and medium term. We also do our best to label entries for clarity and to ease collaboration.

Our actionable item policy has some important consequences, such as:

  • Proposing new features as well as requests for support, help, and guidance must be done in their own spaces, detailed next.

  • Issues we have identified to be outside of Elixir's scope, such as an upstream bug, will be closed (and requested to be moved elsewhere if appropriate).

  • We actively close unrelated and non-actionable issues to keep the issues tracker tidy. If you believe we got something wrong, drop a comment and we can always reopen the issue.

By keeping the overall issues tracker tidy and organized, the community can easily peak at what is coming in new releases and also get involved by commenting on existing issues and submitting pull requests. Please remember to keep the tone positive and be kind! For more information, see the Code of Conduct.

Discussions, support, and help

For general discussions, support, and help, please use the community spaces listed on the sidebar of the Elixir website, such as forums, chat platforms, etc, where the wider community will be available to help you.

Proposing new features

We encourage you to first propose new features in the community spaces listed above. These discussions help refine ideas and gather feedback before submission. Our website also includes a general outline of the language history and its current development focus.

Once you are ready, you can submit your proposal to the Elixir Core mailing list, either through the web interface or by subscribing to it at elixir-lang-core+subscribe@googlegroups.com. Remember to include a clear problem description, compare the proposed solution to existing alternatives in the Elixir ecosystem (and in other languages if possible), and consider the potential impact your changes will have on the codebase and community.

Once a proposal is accepted, it will be added to the issue tracker. Features and bug fixes that have already been merged and will be included in the next release are then "closed" and added to the changelog before release.

Compiling from source

For the many different ways to install Elixir, see our installation instructions on the website. However, if you want to contribute to Elixir, you will need to compile from source.

First, install Erlang. After that, clone this repository to your machine, compile and test it:

git clone https://github.com/elixir-lang/elixir.git
cd elixir
make

Note: if you are running on Windows, this article includes important notes for compiling Elixir from source on Windows.

In case you want to use this Elixir version as your system version, you need to add the bin directory to your PATH environment variable.

When updating the repository, you may want to run make clean before recompiling. For deterministic builds, you should set the environment variable ERL_COMPILER_OPTIONS=deterministic.

Contributing

Contributions to Elixir are always welcome! Before you get started, please check out our CONTRIBUTING.md file. There you will find detailed guidelines on how to set up your environment, run the test suite, format your code, and submit pull requests. We also include information on our review process, licensing requirements, and helpful tips to ensure a smooth contribution experience.

Development links

License

"Elixir" and the Elixir logo are registered trademarks of The Elixir Team.

Elixir source code is released under Apache License 2.0.

Check LICENSE file for more information.

About

Elixir is a dynamic, functional language for building scalable and maintainable applications

elixir-lang.org/

Resources

Readme
License

Code of conduct

Code of conduct

Contributing

Contributing

Security policy

Security policy
Activity

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - dennym/elixir: Elixir is a dynamic, functional language for building scalable and maintainable applications · GitHub
Skip to content
BranchesTags
Repository files navigation
Elixir logo
CIOpenSSF Best Practices
Elixir is a dynamic, functional language designed for building scalable
and maintainable applications.
For more about Elixir, installation and documentation,
check Elixir's website.
Policies
New releases are announced in the announcement mailing list.
You can subscribe by sending an email to elixir-lang-ann+subscribe@googlegroups.com
and replying to the confirmation email.
All security releases will be tagged with [security]. For more
information, please read our Security Policy.
All interactions in our official communication channels follow our
Code of Conduct.
All contributions are required to conform to our Open Source Policy.
Bug reports
For reporting bugs, visit our issue tracker and follow the steps
for reporting a new issue. Please disclose security vulnerabilities
privately in our Security page.
All currently open bugs related to Elixir are listed in the issues tracker.
The Elixir team uses the issues tracker to focus on actionable items,
including planned enhancements in the short and medium term. We also do
our best to label entries for clarity and to ease collaboration.
Our actionable item policy has some important consequences, such as:
  • Proposing new features as well as requests for support, help, and
guidance must be done in their own spaces, detailed next.
  • Issues we have identified to be outside of Elixir's scope,
such as an upstream bug, will be closed (and requested to be moved
elsewhere if appropriate).
  • We actively close unrelated and non-actionable issues to keep the
issues tracker tidy. If you believe we got something wrong, drop a
comment and we can always reopen the issue.
By keeping the overall issues tracker tidy and organized, the community
can easily peak at what is coming in new releases and also get involved
by commenting on existing issues and submitting pull requests. Please
remember to keep the tone positive and be kind! For more information,
see the Code of Conduct.
Discussions, support, and help
For general discussions, support, and help, please use the community
spaces listed on the sidebar of the Elixir website,
such as forums, chat platforms, etc, where the wider community will be available
to help you.
Proposing new features
We encourage you to first propose new features in the community spaces
listed above. These discussions help refine ideas and gather feedback before
submission. Our website also includes a general outline of the language
history and its current development focus.
Once you are ready, you can submit your proposal to the Elixir Core
mailing list, either through the web interface or by subscribing to
it at elixir-lang-core+subscribe@googlegroups.com. Remember to include
a clear problem description, compare the proposed solution to existing
alternatives in the Elixir ecosystem (and in other languages if possible),
and consider the potential impact your changes will have on the codebase and
community.
Once a proposal is accepted, it will be added to the issue tracker.
Features and bug fixes that have already been merged and will be included
in the next release are then "closed" and added to the changelog
before release.
Compiling from source
For the many different ways to install Elixir,
see our installation instructions on the website.
However, if you want to contribute to Elixir, you will need to compile from source.
First, install Erlang.
After that, clone this repository to your machine, compile and test it:
git clone https://github.com/elixir-lang/elixir.git
cd elixir
make
Note: if you are running on Windows,
this article includes important notes for compiling Elixir from source
on Windows.
In case you want to use this Elixir version as your system version,
you need to add the bin directory to your PATH environment variable.
When updating the repository, you may want to run make clean before
recompiling. For deterministic builds, you should set the environment
variable ERL_COMPILER_OPTIONS=deterministic.
Contributing
Contributions to Elixir are always welcome! Before you get started, please check
out our CONTRIBUTING.md file. There you will find detailed
guidelines on how to set up your environment, run the test suite, format your
code, and submit pull requests. We also include information on our review
process, licensing requirements, and helpful tips to ensure a smooth
contribution experience.
Development links
License
"Elixir" and the Elixir logo are registered trademarks of The Elixir Team.
Elixir source code is released under Apache License 2.0.
Check LICENSE file for more information.
About
Elixir is a dynamic, functional language for building scalable and maintainable applications
elixir-lang.org/
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Security policy
Security policy
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - dennym/elixir: Elixir is a dynamic, functional language for building scalable and maintainable applications · GitHub
Skip to content
BranchesTags
Repository files navigation
Elixir logo
CIOpenSSF Best Practices
Elixir is a dynamic, functional language designed for building scalable
and maintainable applications.
For more about Elixir, installation and documentation,
check Elixir's website.
Policies
New releases are announced in the announcement mailing list.
You can subscribe by sending an email to elixir-lang-ann+subscribe@googlegroups.com
and replying to the confirmation email.
All security releases will be tagged with [security]. For more
information, please read our Security Policy.
All interactions in our official communication channels follow our
Code of Conduct.
All contributions are required to conform to our Open Source Policy.
Bug reports
For reporting bugs, visit our issue tracker and follow the steps
for reporting a new issue. Please disclose security vulnerabilities
privately in our Security page.
All currently open bugs related to Elixir are listed in the issues tracker.
The Elixir team uses the issues tracker to focus on actionable items,
including planned enhancements in the short and medium term. We also do
our best to label entries for clarity and to ease collaboration.
Our actionable item policy has some important consequences, such as:
  • Proposing new features as well as requests for support, help, and
guidance must be done in their own spaces, detailed next.
  • Issues we have identified to be outside of Elixir's scope,
such as an upstream bug, will be closed (and requested to be moved
elsewhere if appropriate).
  • We actively close unrelated and non-actionable issues to keep the
issues tracker tidy. If you believe we got something wrong, drop a
comment and we can always reopen the issue.
By keeping the overall issues tracker tidy and organized, the community
can easily peak at what is coming in new releases and also get involved
by commenting on existing issues and submitting pull requests. Please
remember to keep the tone positive and be kind! For more information,
see the Code of Conduct.
Discussions, support, and help
For general discussions, support, and help, please use the community
spaces listed on the sidebar of the Elixir website,
such as forums, chat platforms, etc, where the wider community will be available
to help you.
Proposing new features
We encourage you to first propose new features in the community spaces
listed above. These discussions help refine ideas and gather feedback before
submission. Our website also includes a general outline of the language
history and its current development focus.
Once you are ready, you can submit your proposal to the Elixir Core
mailing list, either through the web interface or by subscribing to
it at elixir-lang-core+subscribe@googlegroups.com. Remember to include
a clear problem description, compare the proposed solution to existing
alternatives in the Elixir ecosystem (and in other languages if possible),
and consider the potential impact your changes will have on the codebase and
community.
Once a proposal is accepted, it will be added to the issue tracker.
Features and bug fixes that have already been merged and will be included
in the next release are then "closed" and added to the changelog
before release.
Compiling from source
For the many different ways to install Elixir,
see our installation instructions on the website.
However, if you want to contribute to Elixir, you will need to compile from source.
First, install Erlang.
After that, clone this repository to your machine, compile and test it:
git clone https://github.com/elixir-lang/elixir.git
cd elixir
make
Note: if you are running on Windows,
this article includes important notes for compiling Elixir from source
on Windows.
In case you want to use this Elixir version as your system version,
you need to add the bin directory to your PATH environment variable.
When updating the repository, you may want to run make clean before
recompiling. For deterministic builds, you should set the environment
variable ERL_COMPILER_OPTIONS=deterministic.
Contributing
Contributions to Elixir are always welcome! Before you get started, please check
out our CONTRIBUTING.md file. There you will find detailed
guidelines on how to set up your environment, run the test suite, format your
code, and submit pull requests. We also include information on our review
process, licensing requirements, and helpful tips to ensure a smooth
contribution experience.
Development links
License
"Elixir" and the Elixir logo are registered trademarks of The Elixir Team.
Elixir source code is released under Apache License 2.0.
Check LICENSE file for more information.
About
Elixir is a dynamic, functional language for building scalable and maintainable applications
elixir-lang.org/
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Security policy
Security policy
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - dennym/elixir: Elixir is a dynamic, functional language for building scalable and maintainable applications · GitHub
Skip to content
BranchesTags
Repository files navigation
Elixir logo
CIOpenSSF Best Practices
Elixir is a dynamic, functional language designed for building scalable
and maintainable applications.
For more about Elixir, installation and documentation,
check Elixir's website.
Policies
New releases are announced in the announcement mailing list.
You can subscribe by sending an email to elixir-lang-ann+subscribe@googlegroups.com
and replying to the confirmation email.
All security releases will be tagged with [security]. For more
information, please read our Security Policy.
All interactions in our official communication channels follow our
Code of Conduct.
All contributions are required to conform to our Open Source Policy.
Bug reports
For reporting bugs, visit our issue tracker and follow the steps
for reporting a new issue. Please disclose security vulnerabilities
privately in our Security page.
All currently open bugs related to Elixir are listed in the issues tracker.
The Elixir team uses the issues tracker to focus on actionable items,
including planned enhancements in the short and medium term. We also do
our best to label entries for clarity and to ease collaboration.
Our actionable item policy has some important consequences, such as:
  • Proposing new features as well as requests for support, help, and
guidance must be done in their own spaces, detailed next.
  • Issues we have identified to be outside of Elixir's scope,
such as an upstream bug, will be closed (and requested to be moved
elsewhere if appropriate).
  • We actively close unrelated and non-actionable issues to keep the
issues tracker tidy. If you believe we got something wrong, drop a
comment and we can always reopen the issue.
By keeping the overall issues tracker tidy and organized, the community
can easily peak at what is coming in new releases and also get involved
by commenting on existing issues and submitting pull requests. Please
remember to keep the tone positive and be kind! For more information,
see the Code of Conduct.
Discussions, support, and help
For general discussions, support, and help, please use the community
spaces listed on the sidebar of the Elixir website,
such as forums, chat platforms, etc, where the wider community will be available
to help you.
Proposing new features
We encourage you to first propose new features in the community spaces
listed above. These discussions help refine ideas and gather feedback before
submission. Our website also includes a general outline of the language
history and its current development focus.
Once you are ready, you can submit your proposal to the Elixir Core
mailing list, either through the web interface or by subscribing to
it at elixir-lang-core+subscribe@googlegroups.com. Remember to include
a clear problem description, compare the proposed solution to existing
alternatives in the Elixir ecosystem (and in other languages if possible),
and consider the potential impact your changes will have on the codebase and
community.
Once a proposal is accepted, it will be added to the issue tracker.
Features and bug fixes that have already been merged and will be included
in the next release are then "closed" and added to the changelog
before release.
Compiling from source
For the many different ways to install Elixir,
see our installation instructions on the website.
However, if you want to contribute to Elixir, you will need to compile from source.
First, install Erlang.
After that, clone this repository to your machine, compile and test it:
git clone https://github.com/elixir-lang/elixir.git
cd elixir
make
Note: if you are running on Windows,
this article includes important notes for compiling Elixir from source
on Windows.
In case you want to use this Elixir version as your system version,
you need to add the bin directory to your PATH environment variable.
When updating the repository, you may want to run make clean before
recompiling. For deterministic builds, you should set the environment
variable ERL_COMPILER_OPTIONS=deterministic.
Contributing
Contributions to Elixir are always welcome! Before you get started, please check
out our CONTRIBUTING.md file. There you will find detailed
guidelines on how to set up your environment, run the test suite, format your
code, and submit pull requests. We also include information on our review
process, licensing requirements, and helpful tips to ensure a smooth
contribution experience.
Development links
License
"Elixir" and the Elixir logo are registered trademarks of The Elixir Team.
Elixir source code is released under Apache License 2.0.
Check LICENSE file for more information.
About
Elixir is a dynamic, functional language for building scalable and maintainable applications
elixir-lang.org/
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Security policy
Security policy
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
GitHub - dennym/elixir: Elixir is a dynamic, functional language for building scalable and maintainable applications · GitHub
Skip to content
BranchesTags
Repository files navigation
Elixir logo
CIOpenSSF Best Practices
Elixir is a dynamic, functional language designed for building scalable
and maintainable applications.
For more about Elixir, installation and documentation,
check Elixir's website.
Policies
New releases are announced in the announcement mailing list.
You can subscribe by sending an email to elixir-lang-ann+subscribe@googlegroups.com
and replying to the confirmation email.
All security releases will be tagged with [security]. For more
information, please read our Security Policy.
All interactions in our official communication channels follow our
Code of Conduct.
All contributions are required to conform to our Open Source Policy.
Bug reports
For reporting bugs, visit our issue tracker and follow the steps
for reporting a new issue. Please disclose security vulnerabilities
privately in our Security page.
All currently open bugs related to Elixir are listed in the issues tracker.
The Elixir team uses the issues tracker to focus on actionable items,
including planned enhancements in the short and medium term. We also do
our best to label entries for clarity and to ease collaboration.
Our actionable item policy has some important consequences, such as:
  • Proposing new features as well as requests for support, help, and
guidance must be done in their own spaces, detailed next.
  • Issues we have identified to be outside of Elixir's scope,
such as an upstream bug, will be closed (and requested to be moved
elsewhere if appropriate).
  • We actively close unrelated and non-actionable issues to keep the
issues tracker tidy. If you believe we got something wrong, drop a
comment and we can always reopen the issue.
By keeping the overall issues tracker tidy and organized, the community
can easily peak at what is coming in new releases and also get involved
by commenting on existing issues and submitting pull requests. Please
remember to keep the tone positive and be kind! For more information,
see the Code of Conduct.
Discussions, support, and help
For general discussions, support, and help, please use the community
spaces listed on the sidebar of the Elixir website,
such as forums, chat platforms, etc, where the wider community will be available
to help you.
Proposing new features
We encourage you to first propose new features in the community spaces
listed above. These discussions help refine ideas and gather feedback before
submission. Our website also includes a general outline of the language
history and its current development focus.
Once you are ready, you can submit your proposal to the Elixir Core
mailing list, either through the web interface or by subscribing to
it at elixir-lang-core+subscribe@googlegroups.com. Remember to include
a clear problem description, compare the proposed solution to existing
alternatives in the Elixir ecosystem (and in other languages if possible),
and consider the potential impact your changes will have on the codebase and
community.
Once a proposal is accepted, it will be added to the issue tracker.
Features and bug fixes that have already been merged and will be included
in the next release are then "closed" and added to the changelog
before release.
Compiling from source
For the many different ways to install Elixir,
see our installation instructions on the website.
However, if you want to contribute to Elixir, you will need to compile from source.
First, install Erlang.
After that, clone this repository to your machine, compile and test it:
git clone https://github.com/elixir-lang/elixir.git
cd elixir
make
Note: if you are running on Windows,
this article includes important notes for compiling Elixir from source
on Windows.
In case you want to use this Elixir version as your system version,
you need to add the bin directory to your PATH environment variable.
When updating the repository, you may want to run make clean before
recompiling. For deterministic builds, you should set the environment
variable ERL_COMPILER_OPTIONS=deterministic.
Contributing
Contributions to Elixir are always welcome! Before you get started, please check
out our CONTRIBUTING.md file. There you will find detailed
guidelines on how to set up your environment, run the test suite, format your
code, and submit pull requests. We also include information on our review
process, licensing requirements, and helpful tips to ensure a smooth
contribution experience.
Development links
License
"Elixir" and the Elixir logo are registered trademarks of The Elixir Team.
Elixir source code is released under Apache License 2.0.
Check LICENSE file for more information.
About
Elixir is a dynamic, functional language for building scalable and maintainable applications
elixir-lang.org/
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Security policy
Security policy
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - dennym/elixir: Elixir is a dynamic, functional language for building scalable and maintainable applications · GitHub
Skip to content
BranchesTags
Repository files navigation
Elixir logo
CIOpenSSF Best Practices
Elixir is a dynamic, functional language designed for building scalable
and maintainable applications.
For more about Elixir, installation and documentation,
check Elixir's website.
Policies
New releases are announced in the announcement mailing list.
You can subscribe by sending an email to elixir-lang-ann+subscribe@googlegroups.com
and replying to the confirmation email.
All security releases will be tagged with [security]. For more
information, please read our Security Policy.
All interactions in our official communication channels follow our
Code of Conduct.
All contributions are required to conform to our Open Source Policy.
Bug reports
For reporting bugs, visit our issue tracker and follow the steps
for reporting a new issue. Please disclose security vulnerabilities
privately in our Security page.
All currently open bugs related to Elixir are listed in the issues tracker.
The Elixir team uses the issues tracker to focus on actionable items,
including planned enhancements in the short and medium term. We also do
our best to label entries for clarity and to ease collaboration.
Our actionable item policy has some important consequences, such as:
  • Proposing new features as well as requests for support, help, and
guidance must be done in their own spaces, detailed next.
  • Issues we have identified to be outside of Elixir's scope,
such as an upstream bug, will be closed (and requested to be moved
elsewhere if appropriate).
  • We actively close unrelated and non-actionable issues to keep the
issues tracker tidy. If you believe we got something wrong, drop a
comment and we can always reopen the issue.
By keeping the overall issues tracker tidy and organized, the community
can easily peak at what is coming in new releases and also get involved
by commenting on existing issues and submitting pull requests. Please
remember to keep the tone positive and be kind! For more information,
see the Code of Conduct.
Discussions, support, and help
For general discussions, support, and help, please use the community
spaces listed on the sidebar of the Elixir website,
such as forums, chat platforms, etc, where the wider community will be available
to help you.
Proposing new features
We encourage you to first propose new features in the community spaces
listed above. These discussions help refine ideas and gather feedback before
submission. Our website also includes a general outline of the language
history and its current development focus.
Once you are ready, you can submit your proposal to the Elixir Core
mailing list, either through the web interface or by subscribing to
it at elixir-lang-core+subscribe@googlegroups.com. Remember to include
a clear problem description, compare the proposed solution to existing
alternatives in the Elixir ecosystem (and in other languages if possible),
and consider the potential impact your changes will have on the codebase and
community.
Once a proposal is accepted, it will be added to the issue tracker.
Features and bug fixes that have already been merged and will be included
in the next release are then "closed" and added to the changelog
before release.
Compiling from source
For the many different ways to install Elixir,
see our installation instructions on the website.
However, if you want to contribute to Elixir, you will need to compile from source.
First, install Erlang.
After that, clone this repository to your machine, compile and test it:
git clone https://github.com/elixir-lang/elixir.git
cd elixir
make
Note: if you are running on Windows,
this article includes important notes for compiling Elixir from source
on Windows.
In case you want to use this Elixir version as your system version,
you need to add the bin directory to your PATH environment variable.
When updating the repository, you may want to run make clean before
recompiling. For deterministic builds, you should set the environment
variable ERL_COMPILER_OPTIONS=deterministic.
Contributing
Contributions to Elixir are always welcome! Before you get started, please check
out our CONTRIBUTING.md file. There you will find detailed
guidelines on how to set up your environment, run the test suite, format your
code, and submit pull requests. We also include information on our review
process, licensing requirements, and helpful tips to ensure a smooth
contribution experience.
Development links
License
"Elixir" and the Elixir logo are registered trademarks of The Elixir Team.
Elixir source code is released under Apache License 2.0.
Check LICENSE file for more information.
About
Elixir is a dynamic, functional language for building scalable and maintainable applications
elixir-lang.org/
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Security policy
Security policy
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
GitHub - dennym/elixir: Elixir is a dynamic, functional language for building scalable and maintainable applications · GitHub
Skip to content
BranchesTags
Repository files navigation
Elixir logo
CIOpenSSF Best Practices
Elixir is a dynamic, functional language designed for building scalable
and maintainable applications.
For more about Elixir, installation and documentation,
check Elixir's website.
Policies
New releases are announced in the announcement mailing list.
You can subscribe by sending an email to elixir-lang-ann+subscribe@googlegroups.com
and replying to the confirmation email.
All security releases will be tagged with [security]. For more
information, please read our Security Policy.
All interactions in our official communication channels follow our
Code of Conduct.
All contributions are required to conform to our Open Source Policy.
Bug reports
For reporting bugs, visit our issue tracker and follow the steps
for reporting a new issue. Please disclose security vulnerabilities
privately in our Security page.
All currently open bugs related to Elixir are listed in the issues tracker.
The Elixir team uses the issues tracker to focus on actionable items,
including planned enhancements in the short and medium term. We also do
our best to label entries for clarity and to ease collaboration.
Our actionable item policy has some important consequences, such as:
  • Proposing new features as well as requests for support, help, and
guidance must be done in their own spaces, detailed next.
  • Issues we have identified to be outside of Elixir's scope,
such as an upstream bug, will be closed (and requested to be moved
elsewhere if appropriate).
  • We actively close unrelated and non-actionable issues to keep the
issues tracker tidy. If you believe we got something wrong, drop a
comment and we can always reopen the issue.
By keeping the overall issues tracker tidy and organized, the community
can easily peak at what is coming in new releases and also get involved
by commenting on existing issues and submitting pull requests. Please
remember to keep the tone positive and be kind! For more information,
see the Code of Conduct.
Discussions, support, and help
For general discussions, support, and help, please use the community
spaces listed on the sidebar of the Elixir website,
such as forums, chat platforms, etc, where the wider community will be available
to help you.
Proposing new features
We encourage you to first propose new features in the community spaces
listed above. These discussions help refine ideas and gather feedback before
submission. Our website also includes a general outline of the language
history and its current development focus.
Once you are ready, you can submit your proposal to the Elixir Core
mailing list, either through the web interface or by subscribing to
it at elixir-lang-core+subscribe@googlegroups.com. Remember to include
a clear problem description, compare the proposed solution to existing
alternatives in the Elixir ecosystem (and in other languages if possible),
and consider the potential impact your changes will have on the codebase and
community.
Once a proposal is accepted, it will be added to the issue tracker.
Features and bug fixes that have already been merged and will be included
in the next release are then "closed" and added to the changelog
before release.
Compiling from source
For the many different ways to install Elixir,
see our installation instructions on the website.
However, if you want to contribute to Elixir, you will need to compile from source.
First, install Erlang.
After that, clone this repository to your machine, compile and test it:
git clone https://github.com/elixir-lang/elixir.git
cd elixir
make
Note: if you are running on Windows,
this article includes important notes for compiling Elixir from source
on Windows.
In case you want to use this Elixir version as your system version,
you need to add the bin directory to your PATH environment variable.
When updating the repository, you may want to run make clean before
recompiling. For deterministic builds, you should set the environment
variable ERL_COMPILER_OPTIONS=deterministic.
Contributing
Contributions to Elixir are always welcome! Before you get started, please check
out our CONTRIBUTING.md file. There you will find detailed
guidelines on how to set up your environment, run the test suite, format your
code, and submit pull requests. We also include information on our review
process, licensing requirements, and helpful tips to ensure a smooth
contribution experience.
Development links
License
"Elixir" and the Elixir logo are registered trademarks of The Elixir Team.
Elixir source code is released under Apache License 2.0.
Check LICENSE file for more information.
About
Elixir is a dynamic, functional language for building scalable and maintainable applications
elixir-lang.org/
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Security policy
Security policy
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages

, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
GitHub - dennym/elixir: Elixir is a dynamic, functional language for building scalable and maintainable applications · GitHub
Skip to content
BranchesTags
Repository files navigation
Elixir logo
CIOpenSSF Best Practices
Elixir is a dynamic, functional language designed for building scalable
and maintainable applications.
For more about Elixir, installation and documentation,
check Elixir's website.
Policies
New releases are announced in the announcement mailing list.
You can subscribe by sending an email to elixir-lang-ann+subscribe@googlegroups.com
and replying to the confirmation email.
All security releases will be tagged with [security]. For more
information, please read our Security Policy.
All interactions in our official communication channels follow our
Code of Conduct.
All contributions are required to conform to our Open Source Policy.
Bug reports
For reporting bugs, visit our issue tracker and follow the steps
for reporting a new issue. Please disclose security vulnerabilities
privately in our Security page.
All currently open bugs related to Elixir are listed in the issues tracker.
The Elixir team uses the issues tracker to focus on actionable items,
including planned enhancements in the short and medium term. We also do
our best to label entries for clarity and to ease collaboration.
Our actionable item policy has some important consequences, such as:
  • Proposing new features as well as requests for support, help, and
guidance must be done in their own spaces, detailed next.
  • Issues we have identified to be outside of Elixir's scope,
such as an upstream bug, will be closed (and requested to be moved
elsewhere if appropriate).
  • We actively close unrelated and non-actionable issues to keep the
issues tracker tidy. If you believe we got something wrong, drop a
comment and we can always reopen the issue.
By keeping the overall issues tracker tidy and organized, the community
can easily peak at what is coming in new releases and also get involved
by commenting on existing issues and submitting pull requests. Please
remember to keep the tone positive and be kind! For more information,
see the Code of Conduct.
Discussions, support, and help
For general discussions, support, and help, please use the community
spaces listed on the sidebar of the Elixir website,
such as forums, chat platforms, etc, where the wider community will be available
to help you.
Proposing new features
We encourage you to first propose new features in the community spaces
listed above. These discussions help refine ideas and gather feedback before
submission. Our website also includes a general outline of the language
history and its current development focus.
Once you are ready, you can submit your proposal to the Elixir Core
mailing list, either through the web interface or by subscribing to
it at elixir-lang-core+subscribe@googlegroups.com. Remember to include
a clear problem description, compare the proposed solution to existing
alternatives in the Elixir ecosystem (and in other languages if possible),
and consider the potential impact your changes will have on the codebase and
community.
Once a proposal is accepted, it will be added to the issue tracker.
Features and bug fixes that have already been merged and will be included
in the next release are then "closed" and added to the changelog
before release.
Compiling from source
For the many different ways to install Elixir,
see our installation instructions on the website.
However, if you want to contribute to Elixir, you will need to compile from source.
First, install Erlang.
After that, clone this repository to your machine, compile and test it:
git clone https://github.com/elixir-lang/elixir.git
cd elixir
make
Note: if you are running on Windows,
this article includes important notes for compiling Elixir from source
on Windows.
In case you want to use this Elixir version as your system version,
you need to add the bin directory to your PATH environment variable.
When updating the repository, you may want to run make clean before
recompiling. For deterministic builds, you should set the environment
variable ERL_COMPILER_OPTIONS=deterministic.
Contributing
Contributions to Elixir are always welcome! Before you get started, please check
out our CONTRIBUTING.md file. There you will find detailed
guidelines on how to set up your environment, run the test suite, format your
code, and submit pull requests. We also include information on our review
process, licensing requirements, and helpful tips to ensure a smooth
contribution experience.
Development links
License
"Elixir" and the Elixir logo are registered trademarks of The Elixir Team.
Elixir source code is released under Apache License 2.0.
Check LICENSE file for more information.
About
Elixir is a dynamic, functional language for building scalable and maintainable applications
elixir-lang.org/
Resources
Readme
License
Code of conduct
Code of conduct
Contributing
Contributing
Security policy
Security policy
Activity
Stars
0 stars
Watchers
0 watching
Forks
0 forks
Report repository
Releases
Packages
Contributors
Languages