Skip to content

Instantly share code, notes, and snippets.

@Kuniwak
Created December 16, 2014 01:14
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Kuniwak/d6107b55dd50589f6783 to your computer and use it in GitHub Desktop.
Save Kuniwak/d6107b55dd50589f6783 to your computer and use it in GitHub Desktop.
  1. identifier が定義・参照・静的解析不能を判別
    • IdentifierClassifier
    • IdentifierCollector
  2. Scope chain を作成
    • ScopeStore
  3. declaring identifier を scope に登録、scope を referencing identifier に登録
    • ScopeLinker
  4. referencing identifier から declaring identifier に到達可能かどうかを調べる
    • ParentAttacher
    • ReferenceReachabilityTester
  5. 未参照 declaring identifier と 未解決 referencing identifier を取得
@Kuniwak
Copy link
Author

Kuniwak commented Dec 16, 2014

Promise のときのノウハウと同じように、個々のプラグインが自身の動作条件を整えるというニュアンスで、前のプラグインを呼び出すと使い勝手がよくなりそう。

ただ、あいかわらず unit test が書きづらい問題は解決しなさそう。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment