f53376cea1
This adds a giant missing piece of the language: proper function values! It is lovely to now understand why early programming language designers didn't implement these, but a joy to now reap the benefits of them. In adding these, many other changes had to be made to get them to "fit" correctly. This improved the code and fixed a number of bugs. Unfortunately this touched many areas of the code, and since I was learning how to do all of this for the first time, I've squashed most of my work into a single commit. Some more information: * This adds over 70 new tests to verify the new functionality. * Functions, global variables, and classes can all be implemented natively in mcl and built into core packages. * A new compiler step called "Ordering" was added. It is called by the SetScope step, and determines statement ordering and shadowing precedence formally. It helped remove at least one bug and provided the additional analysis required to properly capture variables when implementing function generators and closures. * The type unification code was improved to handle the new cases. * Light copying of Node's allowed our function graphs to be more optimal and share common vertices and edges. For example, if two different closures capture a variable $x, they'll both use the same copy when running the function, since the compiler can prove if they're identical. * Some areas still need improvements, but this is ready for mainstream testing and use!
56 lines
2.0 KiB
Go
56 lines
2.0 KiB
Go
// Mgmt
|
|
// Copyright (C) 2013-2019+ James Shubin and the project contributors
|
|
// Written by James Shubin <james@shubin.ca> and the project contributors
|
|
//
|
|
// This program is free software: you can redistribute it and/or modify
|
|
// it under the terms of the GNU General Public License as published by
|
|
// the Free Software Foundation, either version 3 of the License, or
|
|
// (at your option) any later version.
|
|
//
|
|
// This program is distributed in the hope that it will be useful,
|
|
// but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
// GNU General Public License for more details.
|
|
//
|
|
// You should have received a copy of the GNU General Public License
|
|
// along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
// Package errwrap contains some error helpers.
|
|
package errwrap
|
|
|
|
import (
|
|
"github.com/hashicorp/go-multierror"
|
|
"github.com/pkg/errors"
|
|
)
|
|
|
|
// Wrapf adds a new error onto an existing chain of errors. If the new error to
|
|
// be added is nil, then the old error is returned unchanged.
|
|
func Wrapf(err error, format string, args ...interface{}) error {
|
|
return errors.Wrapf(err, format, args...)
|
|
}
|
|
|
|
// Append can be used to safely append an error onto an existing one. If you
|
|
// pass in a nil error to append, the existing error will be returned unchanged.
|
|
// If the existing error is already nil, then the new error will be returned
|
|
// unchanged. This makes it easy to use Append as a safe `reterr += err`, when
|
|
// you don't know if either is nil or not.
|
|
func Append(reterr, err error) error {
|
|
if reterr == nil { // keep it simple, pass it through
|
|
return err // which might even be nil
|
|
}
|
|
if err == nil { // no error, so don't do anything
|
|
return reterr
|
|
}
|
|
// both are real errors
|
|
return multierror.Append(reterr, err)
|
|
}
|
|
|
|
// String returns a string representation of the error. In particular, if the
|
|
// error is nil, it returns an empty string instead of panicing.
|
|
func String(err error) string {
|
|
if err == nil {
|
|
return ""
|
|
}
|
|
return err.Error()
|
|
}
|