| commit | 69678525c7f5aa2c7653de73ecdfcbf052e163de | |
| author | Lucian Wischik <ljw@fb.com> | |
| Sat, 4 Apr 2020 14:53:18 +0000 (4 07:53 -0700) | ||
| committer | Facebook GitHub Bot <facebook-github-bot@users.noreply.github.com> | |
| Sat, 4 Apr 2020 15:09:26 +0000 (4 08:09 -0700) | ||
| tree | d3f7fc49557a645c6e0e8c45efbf5a622bb099b0 | treesnapshot (tar.gz zip) |
| parent | 3155d9dc9966650ad6c82273d1f244931bcaa563 | commitdiff |
Provider_context.make_entry public
Summary:
sIDE is going to treat entries differently. It will maintain its own list of entries for each opened file, and it will cache each entry's AST and TAST.
But it won't store them in a context. It will only ever construct "singleton" contexts on the fly: when computing the TAST for file A.php, it will construct a singleton context with only an entry for A.php, and it will treat all other files as they are on disk.
This diff is a small step towards that. It allows sIDE to construct entries without them being part of a context.
Reviewed By: arxanas
Differential Revision: D20834156
fbshipit-source-id: e635b5bbfe24327f85296f1433b11382cb84285b
Summary:
sIDE is going to treat entries differently. It will maintain its own list of entries for each opened file, and it will cache each entry's AST and TAST.
But it won't store them in a context. It will only ever construct "singleton" contexts on the fly: when computing the TAST for file A.php, it will construct a singleton context with only an entry for A.php, and it will treat all other files as they are on disk.
This diff is a small step towards that. It allows sIDE to construct entries without them being part of a context.
Reviewed By: arxanas
Differential Revision: D20834156
fbshipit-source-id: e635b5bbfe24327f85296f1433b11382cb84285b
| hphp/hack/src/providers/provider_context.ml | diffblobblamehistory | |
| hphp/hack/src/providers/provider_context.mli | diffblobblamehistory |