Cosmo is a statically-typed interpreted programming language written in pure Crystal.
We have an extension for VS code (source), however it currently only features syntax highlighting and code snippets.
Download the Cosmo Installer and run it.
You can also demo the language using the Cosmo bot in my Discord server.
- R-unic - creator and maintainer
- quasar098 - created socket library
- Kevin Alavik - purchased https://cosmo-lang.dev
There is a guide about how to contribute here on our website.
You can find any documentation you might need to contribute here. It's a page automatically generated by Crystal containing documentation for all classes, modules, etc.
- Fork it
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Test your code (
make test
) - Push to the branch (
make publish
) - Create a new Pull Request
Have any questions or comments? DM me or @ me in my server on Discord.
- Named arguments
- Make a Cosmo->C compiler
- C bindings
- Grammar
- Regexes
- Endless (and beginless?) range literals
- Postfix
every
loop (e.x.x < 1 for every int x in vec
)? typeof
- Multiple assignment/declaration with spreads (e.x.
int x, y = *[1, 2]
) :=
operator (this will include making=
binary expressions a statement [this is gonna be weird to implement lmao])- Enums
- Decorators
- Interfaces
- Namespaces
- Classes
- single inheritance
- mixins
- static/protected members
- Rewrite type system
- bound expressions (!!)
- an actual type pass
- generics
- type inference
- casting union types
- implicit conversions
- intersection types
- Other
- Extend
HTTP
library- routing stuff
+
operator for vectors, same functionality asVector->combine
string
andchar
to hex conversions (e.x.<uint>'f' == 15
)- Some form of multithreading
- Intrinsic methods for all datatypes (inherit from a base type)
- REPL supports multiline source
- Colorize REPL input
- Extend
- Performance boosts lol
- Parser does not recognize imported classes as type (WHY???)
- Access imported aliased types
- Access types within tables (e.x.
JSON::Any
) - More detailed errors when unable to resolve a type
- Import stack traces
- Properly log errors from intrinsics
- Segfaults
- passing
$
? (pretty sure this is just like everything to do with classes) <float[]>[1,2,3]
- passing
- Class instance variables available outside of
$
- Throw if same module was imported twice
["a.b.c"].first.split('.')
tries to access["a.b.c"].first
instead of["a.b.c"].first()
because of thesplit
call with parentheses (bug)
- Chained method calls with optional parentheses (e.x.
["a.b.c"].first.split('.').first == "a"
) - Expectation of errors in parser spec (e.x.
()
throwsInvalid syntax ')': Expected an expression
) - New intrinsic libraries
(empty)
- Package manager (Stars + StarsAPI) (WIP)
- Documentation generator?
- Language server
- Highlight function definition names without parentheses
(empty)