quest
quest copied to clipboard
sampersand
The Quest programming language
# Proposal to Improve Quest's Binary Operator semantics. Currently in Quest there are Unary and Binary operators which collide in names. This is an issue for both those using and...
Currently, the only way to do anything with I/O is to use `system`, eg `$foo_contents = system("cat foo")`... not ideal. It'd be best if we could make some object that...
Add a custom `TypeName` trait that can be used to reference types within Quest code. Currently, `std::any::type_name` is used, but that also reveals internal implementation details (eg `quest_core::types::Boolean`), and so...
Should Objects return `null` instead of throwing an exception if an object that's indexed doesn't exist? By returning `null` we allow for some nifty tricks like `$MAX = if(_0, _0,...
If it did this, we could use `return` as a break statement. Currently, if you want to, you need to wrap the `while` in a block, eg: ```quest $i =...
Hm.. it might be interesting to think about quest without eagerly evaluating everything? This would work well with the block paradigm, and blocks wouldn't be so ubiquitous. But that would...
Should these both exist? Currently, they're both defined within `Kernel` (although `for` just panics because it's not implemented). They can both easily be implemented in terms of `while`—e.g. `while($true, {...
Both of these are crucial for further development, and should be done by no later than alpha. # Roadmap ## Quest Core - [ ] Unit tests - [ ]...
Currently the REPL doens't actually exist. This would be extremely useful for testing simple expressions and stuff. It shouldn't be too hard to get a dumb REPL working; in the...
Way back when, they were used for different ways to call blocks (e.g. `foo ( ... )` vs `foo [ ... ]`), but I've sinced moved away from that. However,...