Improve names

[charleskawczynski]

I think the primary feature of this package will be to collect broadcast expressions into a tuple. There may different ways to construct this tuple, and each approach may have its own limitations and pros/cons (#5). That said, the primary feature of this package is really about constructing these tuples, and we should think about good names for this feature. Currently fused_pairs is not really descriptive in terms of the approach/limitations etc.

Some ideas that come to mind are:

• fused_pairs_basic - the current fused implementation, which is "safe" in that it's less easy to misuse
• fused_pairs_all/fused_pairs_unsafe? - allowed across loops, but cannot contain arbitrary function calls, aliasing (?)

[charleskawczynski]

Maybe local_pairs and nonlocal_pairs?

[charleskawczynski]

Or, maybe:

• @make_fused/@make_fused_once FusedBroadcast fused
• @make_fused_runtime FusedBroadcast runtime_fused
  ?