v2.16.0

Due to a backwards-incompatible change (to the parsing of type constants) in hhvm we tagged a new backwards-incompatible version of hhast, so now we need to tag a new version of definition-finder that requires the new hhvm+hhast.

What's Changed

• Require and support HHVM 4.158 and HHAST by @lexidor in #36

Full Changelog: v2.15.0...v2.16.0

v2.15.0: support and require HHVM 4.157+

Due to a backwards-incompatible change (to the parsing of type constants) in hhvm we tagged a new backwards-incompatible version of hhast, so now we need to tag a new version of definition-finder that requires the new hhvm+hhast.

v2.14.2: support HHVM 4.107

This release adds support for HHVM 4.107, and retains support for HHVM 4.78+

2.14.1: parse union/intersection typehints

Note: Union/intersection typehints are an experimental unstable Hack feature.

2.14.0: support and require HHVM 4.78+

• compatibility fixes for HHVM and HHAST v4.78
• supports and requires the new XHP syntax (xhp class foo instead of class :foo, no automatic "name mangling")

2.13.5: support HHVM and HHAST v4.72

Removes support for array(...) literals (support for [...] literals was already removed in v2.13.3).

2.13.4: permit type-assert v4

This release permits use with type-assert v4; type-assert v3 is also supported.

This release also removes autoloader support for PHP projects; this is not considered a breaking change given that no supported version of HHVM supports PHP.

2.13.3: support HHAST 4.53

Removed reference to HHAST\ArrayCreationExpression which no longer exists.

Permit hhvm-autoload v3.0

hhvm-autoload v2.0 is still compatible.

2.13.1: clean up array literals

No longer depends on the disallow_array_literal setting being turned off, so it can now be used from projects with stricter settings without causing Hack errors.