Skip to content
<open-source>
Oeiuwq Faith Blog OpenSource Porfolio

slibby05/rice

an optimizing curry compiler
Source code at GitHub null
slibby05/rice.json
{
  "createdAt": "2019-05-30T20:10:41Z",
  "defaultBranch": "master",
  "description": "an optimizing curry compiler",
  "fullName": "slibby05/rice",
  "homepage": null,
  "language": "C",
  "name": "rice",
  "pushedAt": "2022-11-27T21:24:15Z",
  "stargazersCount": 14,
  "topics": [],
  "updatedAt": "2025-05-31T05:56:10Z",
  "url": "https://github.com/slibby05/rice"
}

RICE: An Optimizing Curry Compiler

project_description
This is an optimizing compiler for the Curry programming language.

Getting Started

Section titled “Getting Started”

This is an example of how you may give instructions on setting up your project locally. To get a local copy up and running follow these simple example steps.

Prerequisites

Section titled “Prerequisites”

The only requirement is the Pakcs Curry compiler Version 2.3 and the CPM package manager. A version compatible with Pakcs 3.0 and later is currently being developed.

  • pakcs 
    https://www.informatik.uni-kiel.de/~pakcs/download.html

Installation

Section titled “Installation”
  1. Install Pakcs
  2. copy the runtime directory to ~/.rice
  3. Install RICE
    Terminal window
    cypm install

(back to top)

If you’d like to run the benchmarks, use can use the generated C code in the compiled_benchmarks folder. You can build the programs with make. Otherwise you can compile the bunchmarks from the Curry source in the benchmarks folder using the runBenchmarks script.

All benchmarks are built with the clang compiler. They all compile with GCC, but they run faster with Clang.

Usage

Section titled “Usage”
Terminal window
rice File.curry

If File.curry contains a main method, then rice will produce an executable, otherwise it will just compile the library.

(back to top)

Roadmap

Section titled “Roadmap”
  • Compatibility with Pakcs 3.0

(back to top)

Contributing

Section titled “Contributing”

If you have a suggestion that would make this better, please fork the repo and create a pull request.

  1. Fork the Project
  2. Create your Feature Branch (git checkout -b feature/Feature)
  3. Commit your Changes (git commit -m 'Add some Feature')
  4. Push to the Branch (git push origin feature/Feature)
  5. Open a Pull Request

(back to top)

Contact

Section titled “Contact”

Steven Libby - libbys@up.edu

Project Link: https://github.com/slibby05/rice

(back to top)