Awsum

Community

Two things from the Awsum organization: news on the channels below, and we can come talk at your meetup, podcast, or conference.

Forums, chat rooms, and anything that needs moderation — for you or anyone else to run.

Conferences, meetups, podcasts

We'd love to participate (online works best on our end) — here are some directions we could take it:

Functional programming, more broadly — what the paradigm buys you.
What Awsum guarantees, and how the language is shaped to do it.
How defunctionalization makes higher-order code and non-tail recursion stack-safe on every backend.
Automatic static lifetimes for a functional language on LLVM and WASM — no lifetime syntax in user code.
How the compiler turns one Core IR into five backends.
Software reliability for the people paying for it — what to ask, and what's actually achievable.

DM on any of the channels below with a rough date and what your audience is into.

Follow

Report bugs, contribute code

Every public repository in the awsum-lang organization has its own issue tracker for bug reports and feature requests. For the compiler itself, open an issue at github.com/awsum-lang/awsum/issues.

For code contributions, see CONTRIBUTING.md in any repository — development setup, signed-commit policy, and PR conventions.

Report security issues

Suspected security vulnerabilities go through a private channel — not through the public issue tracker. The preferred route is GitHub Private Vulnerability Reporting: github.com/awsum-lang/awsum/security/advisories/new. Fallback channel and full policy (scope, supported versions, response timeline) are in SECURITY.md.