Issues - vilinski/nemerle GitHub Wiki

Table of Contents Introduction Submitting bug reports Misleading error messages Submitting feature request Why is it important to report an issue?

We track issues in Mantis bug tracker. This page explains what, when and why should be reported there.

There is a mailing list tracking activity in the bug tracker.

• Best bug reports include patches :-)
• Good bug reports include a small, self-contained example of code and the short description of what's the expected and actual behavior.
• Any other bug reports are also accepted. We will try our best to find a solution for you.

If the code is short (say under 50 lines), please paste it directly to the description. Otherwise use file upload. Patches should be always uploaded as files and never pasted.

Checkpoints for creating a good bugreport are:

1. Provide actual results you get for the testcase
2. If the test involves libraries or assemblies that are not part of the framework, add infomation on where to download all dependencies, and how to compile/install them.
3. If compiling the test case requires more than: ncc test.n provide the full command line you used to compile the test.
4. Provide info about the version of the software you're using (both ncc and the .NET runtime).
5. Provide the output you expect the test case to produce.
6. You can post the info about bugreport to the mailing list, so it gets more notice from other users and may trigger futher discussion. This relates especially to feature requests.

...are bugs and should be reported.

Error message from functional language compilers, especially the ones featuring type inference, are often very poor. Because we aim Nemerle to be not that difficult language for newcomers, we would like the error reports to be as accurate as possible.

So if you find a particular error message to be misleading, or you see possibility for it to be more descriptive, please take a time to report this as a bug.

Small test cases illustrating the problem are most welcome here, but some general description of the code causing the error and the error message, pasted exactly will also do.

We want Nemerle to be a better language. Your suggestions can help make it happen. Therefore if you have an idea for a new language (or library, or macro library) feature, please take your time to share it with us.

It is mostly good idea to discuss a feature before submitting it to the issue tracker. You can do it by email or on IRC, please have a look a the Authors and Contact page for more information.

We use Mantis as a tool to organize our work. That is we look at the bug list and decide what to do next. Therefore even if you talked to a developer (private email, mailing list, IRC, Jabber whatever), you are still encouraged to report the issue to the Mantis. Otherwise it might get lost.