Foo Far created SLF4J-471:
-----------------------------
Summary: CharSequence and varargs
Key: SLF4J-471
URL: https://jira.qos.ch/browse/SLF4J-471
Project: SLF4J
Issue Type: Bug
Components: Core API
Environment: Could sl4fj provide an interface that enables avoiding
all object allocation?
This is important for low latency applications, which only allocation objects
at startup, in order to prevent even minor collection pauses.
The actual zero-garbage implementation could come later. It would be nice if
the slf4j api itself did not have any such impediments. So e.g. users could
pass some preallocated string-like object which implements CharSequence,
instead of a concrete String, which cannot be allocated ahead of time. There
could also be overloaded methods for relatively few parameters (say up to ten),
for users that want to avoid the array allocation involved in the java variable
argument feature. Of course it'd be positive to have logback implementation so
that those actually work, even if they work with allocations.
For the sake of backwards compatibility, this could be a new java interface.
Perhaps a superinterface with the varargs replacements as default methods, to
avoid breaking anybody who might be implementing the original interface.
Reporter: Foo Far
Assignee: SLF4J developers list
--
This message was sent by Atlassian JIRA
(v7.3.1#73012)
_______________________________________________
slf4j-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/slf4j-dev
