Contact
If you have any questions, comments, suggestions, bug reports, or issues you would like to discuss regarding Mercury, feel free to contact us on one of the mailing lists listed below.
Bug reports may also be added to the bug tracker. If sending a bug report, please enclose as much information as possible, including, if possible source code (such as a small test case that exhibits the bug), any error messages encountered, operating system version, and configuration information, compiler flags used and Mercury compiler version. Also, you might want to check to see if a newer release is available, and look at the bug tracker to check whether the bug has already been reported.
For more detailed information about how to write bug reports that help you as well helping us, see these links:
- How to ask a technical question, Bootcamp 2018
- How to ask technical questions at the Odin project
- The XY problem
- How to ask a technical question the right way
- How to ask good technical questions
If you wish to contact the core team about something that is not suitable for the mailing lists, then e-mail mercury@mercurylang.org User support questions are best handled on the mercury-users mailing list.
Mailing Lists
There are four Mercury mailing lists:
- mercury-announce is a very low-volume list for announcements about things directly related to Mercury, e.g. new versions of the Mercury implementation, tools for Mercury programmers, books about Mercury, etc.
-
The
mercury-users
list is intended for general discussion about Mercury and related matters of
interest to Mercury users.
It is archived and searchable. -
The
mercury-developers
list is intended for general discussion about the development of Mercury and
the Mercury implementation and related matters of interest to the developers of
Mercury.
It is archived and searchable. Note that in recent times, most the actual development discussion seems to be done on the mercury-reviews list, rather than mercury-developers. -
The
mercury-reviews
list is intended for use by the developers of Mercury, for the purpose of
reviewing changes to the Mercury implementation (including documentation, test
suite, etc.) and the Mercury web site. This list is specifically for posting
diffs, reviews of diffs, and discussion of issues raised in such reviews. It
tends to be a fairly high-volume list.
It is archived and searchable. -
The
mercury-ads
list is intended to post things of interest to Mercury developers,
that aren't directly Mercury related.
For example calls for papers for logic programming conferences.
The list is moderated to avoid abuse,
posts for conferences in the wider logical / declarative / functional
community are encouraged.
It tends to be a low-volume list.
It is archived and searchable.
To subscribe or unsubscribe to any of these mailing lists, please use the forms on the respective pages.
To post to one of these lists, send an e-mail to one of the following addresses:
- users@lists.mercurylang.org
- developers@lists.mercurylang.org
- reviews@lists.mercurylang.org
- ads@lists.mercurylang.org, note that there will be some delay while your post is reviewed.
Search the Archives
Please use the search bar below to search the archives:
Other communities and social networks
The @MercuryLang twitter account will make announcements of news, releases and other related things.
IRC
There is a Mercury IRC channel on the
libera.chat
IRC network.
Connect to irc.libera.chat port 6697 with TLS
enabled and join the #mercury channel.
There is a Mercury subreddit on the popular link-sharing site reddit.
stackoverflow.com
stackoverflow.com is a website for developers to ask and answer questions. All Mercury-related questions are tagged with [mercury].
Rosetta Code
A Mercury category has been established on Rosetta Code, a website for sharing implementations of common problems in different languages.
Adventures in Mercury
The Adventures in Mercury blog by Chris King tackles various problems and explains how his elegant Mercury solutions are constructed.
GitHub
Find all projects using Mercury on GitHub.