Below is a list of project ideas for the 2014 GSoC Application for Nimrod. You will need to spend a considerable amount of time experimenting with the Nimrod programming language before you attempt these projects.
**Allow bootstrap-time integration of the nimrod executable with the standard library**
* Allow the nimrod bootstrap process to integrate the nimrod standard library source code and other associated resources into the nimrod binary, to be used by the nimrod binary when compiling source code. The included library modules should be overridable, either by a switch passed to the nimrod executable, or by placing an actually library file in a pre-determined path.
* Allow the fsmonitor module to work on Windows by using native api's to gather information about changes in monitored files and directories.
* Revise the fsmonitor module api to decouple unix/linux file handle paradigms (such as using sockets.poll) from the api, allowing easier implementations of native backends.
* Integrate the fsmonitor module's polling mechanism into the new asynchronous io modules.
* Implement a procedure which uses native stat-like calls on Linux, Mac, Windows, and other operating systems to gather detailed information about specific file system objects. Allow the bypassing of symlinks and hardlinks, where possible.
**Add documentation to the nimrod compiler internals**
* Add comments to the compiler internals, documenting the various mechansisms and mechanics the compiler uses to analyze and transform nimrod code to the code of the specified backend.
* Reduce the number of assumptions the nimrod builder makes about its host system, in order to reduce configuration restrictions. Assumptions include location and usage of external tools, such as git.
**Implement re2nim, a lexer generator for nimrod**
* Model it after re2c or the Ragel state machine generator
**Implement a Nimrod backend for the Ragel state machine generator**