Skip to content

Remove has_feature #523

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.

Sign up for GitHub

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

Merged
titzer merged 1 commit into from
Feb 25, 2016
Merged

Remove has_feature #523

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 0 additions & 13 deletions AstSemantics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -566,19 +566,6 @@ outside the range which rounds to an integer in range) traps.
returns the the first of these two operands if the condition operand is
non-zero, or the second otherwise.

## Feature test

To support [feature testing](FeatureTest.md), an AST node would be provided:

* `has_feature`: return whether the given feature is supported, identified by string

In the MVP, `has_feature` would always return false. As features were added post-MVP,
`has_feature` would start returning true. `has_feature` is a pure function, always
returning the same value for the same string over the lifetime of a single
instance and other related (as defined by the host environment) instances.
See also [feature testing](FeatureTest.md) and
[better feature testing](FutureFeatures.md#better-feature-testing-support).

## Unreachable

* `unreachable`: An expression which can take on any type, and which, if
Expand Down