This is a fairly common pattern when preparing args for a function (and this function gets it wrong by not calling to_str):

pub fn extract(interp: &Artichoke, at: Value) -> Result<Self, Box<dyn RubyException>> {
    let name = at.pretty_name();
    if let Ok(index) = at.clone().try_into::<Int>() {
        Ok(Self::Index(index))
    } else if let Ok(name) = at.clone().try_into::<&

#306 addresses a term-precedence bug with exponentiation. However, we do not have an end-to-end test case for this.
It should be included, ideally for all operators.

The MarkSweep struct implements GcRuntime to facilitate garbage collection for Mun. Currently, the implementation is quite inefficient. One of the things that could be improved is to implement a slab allocator (or object pool) instead of randomly allocating memory through a Pin<Box<ObjectType<T>>>. The general idea of the allocator is to alloc

Describe the bug
Documentation example is broken

To Reproduce
Steps to reproduce the behavior:

1. Go to 'https://github.com/ntrupin/abstractml/tree/master/docs/examples'
2. See error

Expected behavior
The page displays the proper compiled html source

Screenshots
![image](https://user-images.githubusercontent.com/37413895/69005868-b5e55b00-098c-11ea-9442-822dec285555.

When a process has no messages it should be taken off the run queue. Once a message is sent to such a process it should be placed on the run queue again. This prevents pool threads from consuming 100% of the CPU when there are only processes waiting for messages.

പൊളിസാധനം എന്നാണ് മലയാളമെങ്കിലും ഹിറ്റായ ഐറ്റം പൊളിസാനം എന്ന നാടൻ പ്രയോഗമാണ്. വേണമെങ്കില്‍ pwoli_sanam എന്നാക്കാവുന്നതാണ്

Issue, or potential issue

There is little to no documentation at the moment.
As the project starts to grow we can ignore this issue no more.

Potential solutions

Start writing documentation.
As an added bonus, we can start making use of Rust's documentation testing feature.

Additional Context

...

We should parse markdown in the documentation comments, and produce the appropriate markup in the documentation based on that. pulldown-cmark could be useful for this.

Old code: https://github.com/Vengarioth/xshade/blob/master/src/type_system/type_check.rs#L94-L124

• Create a pass in passes/ast/type_checking
• Add function type to symbol table
• Add function as symbol to the symbol table
• Type check arguments
• Type check return type (not if it actually returns the correct type)
• Set call signature for function type
• Test

This would help clarify what you're trying to do with the project.