Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configs: use a uniform syntax without Match exceptions #507

Merged
merged 3 commits into from
Jan 13, 2017

Commits on Jan 12, 2017

  1. Configs: use a uniform syntax without Match exceptions

    The old style of specifying Configs used total functions.  The only way to
    indicate that a key was not matched was to throw an exception.  Not only was
    this a performance concern, but it also caused confusing error messages
    whenever you had a match failure from a lookup within a lookup.  The
    exception could get handled by an outer-lookup that then reported the wrong
    key as missing.
    terpstra committed Jan 12, 2017
    Configuration menu
    Copy the full SHA
    f4869d8 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    58daf97 View commit details
    Browse the repository at this point in the history

Commits on Jan 13, 2017

  1. Configuration menu
    Copy the full SHA
    2da6fe1 View commit details
    Browse the repository at this point in the history