deprecate broadcast_function and broadcast!_function
#16613
Conversation
|
Do you use ack or something configured in a way that skips contrib? |
|
Yes. Also I don't think it makes sense for an editor mode to contain a list of Base exports. Can we remove them so we don't have to keep "maintaining" the list? Only this one editor mode has the list, none of the others do AFAIK. I don't think there is a good reason to color those functions differently. They also seem to be classified as "keywords" along with actual keywords like for, while, etc. so I would say the file is just wrong. |
|
I agree with getting rid of the export lists in various editor modes – functions are just functions. For what it's worth, a good way to search for a pattern in the whole project is git ls-files [<dirs>...] | xargs ack <pattern> |
|
@cormullion seems to be the main author (and presumably, user?) of that file, so ask him? I would of course prefer if these things were all completely autogenerated, and hosted in external repos (JuliaEditorSupport org?). The other editor support files that are still in contrib have lists of some types and functions, but not all exports like that one. |
|
The fact that Base functions are in the same category as |
|
I confess and hang my head in a modest amount of shame: I did stick everything into that BBEdit plist file... More recently I've been using Vim and Atom, and I wasn't intending to keep updating the BBEdit plist file for every future release or writing a script to generate one either. I'd support you removing it now, and if anyone wants to hack on a copy they can shout on the discussion forums... |
|
Thanks for responding. Will give people a bit of time to speak up at https://groups.google.com/forum/?nomobile=true#!topic/julia-users/sQ5Atvjicxw, we'll either delete it or move it to its own repo. |
closes #16601