Hasgo

• Coverage status: gocover.io
• Our report card:

Hasgo is a code generator with functions influenced by Haskell. It comes with some types out-of-the-box so you can start using it without running the generator. Specifically you can start using Hasgo's Strings and Ints types.

We want to focus on being:

• Immutable
• Strongly-Typed (no interface{})
• Nil-safe

Pie

The inspiration for Hasgo, as well as some ideas around implementation come from the lovely Pie library, made by Elliot Chance. It's safe to say that Hasgo would not exist without Pie. However, the way Pie and Hasgo work is not the same and neither is the focus of the project. If you don't find a function in Hasgo, check out Pie! :smiley:

Example

import . "github.com/DylanMeeus/hasgo/types"
func EpicFunction() {
	// create a range of -10 -> 10. Take the absolute values, keep only even numbers, and sum them.
	result := IntRange(-10,10).
		Abs().
		Filter(func(i int64) bool {
			return i % 2 == 0
		}).
		Sum()
	// result = 60 
}

You can find more examples here.

Installation

go get -u github.com/DylanMeeus/hasgo

Or add hasgo to your go.mod file.

require github.com/DylanMeeus/hasgo/v1.0.2

Types

• Ints ([]int64)
• Strings ([]string)

Functions

These are the function currently available with Hasgo. It shows you which type of data they operate on as well as the Haskell type definition. The first symbol of the signature is actually the method receiver in Go terms.

Alternatively, you can consult the godoc

Generic functions

These functions can be generated for every type.

Hardcoded functions

The built-in types (Strings, Ints, Bools) have some functions defined on them that are not generated. Mostly because we could not create them in a generic way.

* (Functions prefixed by a star are functions added to the type itself, where first element in the signature is the method receiver. So for examples, the Equals method is Ints{1,2}.Equals(Ints{1}). But, the IntRange function looks like hasgo.IntRange(0,10).

Contributing

You can help out Hasgo in a variety of ways! Here are some ideas:

• Use Hasgo! :smiley:
• Spread the word (Write a blog, tweet, talk about..)
• Suggest features (Create an issue to make a suggestion)
• Report bugs (Similarly, create an issue)
• Contribute code. (Create a PR, we'll gladly take a look and help you get it merged!)
  • We have separate contribution guidelines

What's in a name?

The name Hasgo is a portmanteau of "Haskell" and "Go". I'm a big fan of both languages, though they are quite different. It's impossible to write real Haskell-like code in Go. There are some obvious differences between the languages in terms of syntax. I hope the functions in this library stay as close as possible to their Haskell implementations. There might be extra functions in here that are not in Haskell, and there will be functions in Haskell that you won't find here.

The inspiration mainly shows in the naming of functions. If the functions were named after Java lambdas, it'd be called "Jago". Sorry if you expected more Haskell goodness (I'm open to suggestions of how more haskell in Hasgo!)

Real Generics?

Currently I have an experimental implementation of hasgo here as hasgo2. It does require a development version of Go installed from source to function correctly at this stage.