@Planeshifter Any thoughts on the package name, here?

@stdlib/array/log with variable name log seems fine with me. Could use logArray. If we were concerned about log being confused with logarithm, another alternative may be print?

@Planeshifter another question is whether this package belongs in @stdlib/array.

After thinking about this a bit more, I am thinking that we should create a new top-level console namespace (i.e., @stdlib/console) for housing this and other console related packages. In which case, this package could be moved to @stdlib/console/log-array (or @stdlib/console/log-each; I think this name is better).

Having a console namespace could be useful, as there is enough variation among console implementations in JS engines that having consistent behavior (i.e., a set of standard APIs) could be useful. These APIs would largely be independent of our planned printf set of APIs.

Prior art

• console-browserify: especially among older engines, having a consistent console API motivated Browserify and other bundlers to ship an interface consistent with what existed in Node.js.

Considerations

• In JS engines, console is a global instance. For APIs supporting labels, these are stored in a global cache (e.g., count, group, etc). We could provide a small enhancement, which would be similar to debug and export a factory method along side the global instance. A factory instance could then maintain its own cache in order to avoid collisions. Individual packages such as console/log, console/error, etc, would simply be wrappers around methods:

  function log() {
      console.log.apply( null, arguments );
  }

  With factories, we'd put the above in a closure and to a bit of magic to make labels work (e.g., console.log( '<label>:%s', msg )) and ensure that the output appeared the same.

Thoughts, @Planeshifter?

@kgryte I think we should go ahead and create a top-level console namespace!

Cool. I'll add the top-level namespace. @steff456 Once I do, we'll want to rename the package in this PR. I'll circle back once we have everything in place.

Ok! I'll wait for the signal 😉

@steff456 The console namespace has now been created. Would you mind renaming this package to

@stdlib/console/log-each

and updating the alias from log to logEach?

You'll need to merge in the latest commits from develop.