51369b610e
When an include is not surrounded by empty lines, its content is inlined on the same line as the adjacent content. That can lead to broken tags and other display issues. This PR fixes all such includes and introduces a validation step that forbids introducing the same problem again.
31 lines
1.1 KiB
Plaintext
31 lines
1.1 KiB
Plaintext
== Why is this an issue?
|
|
|
|
Calling ``++System.gc()++`` or ``++Runtime.getRuntime().gc()++`` is a bad idea for a simple reason: there is no way to know exactly what will be done under the hood by the JVM because the behavior will depend on its vendor, version and options:
|
|
|
|
* Will the whole application be frozen during the call?
|
|
* Is the ``++-XX:DisableExplicitGC++`` option activated?
|
|
* Will the JVM simply ignore the call?
|
|
* ...
|
|
|
|
Like for ``++System.gc()++``, there is no reason to manually call ``++runFinalization()++`` to force the call of finalization methods of any objects pending finalization.
|
|
|
|
|
|
An application relying on these unpredictable methods is also unpredictable and therefore broken. The task of running the garbage collector and calling ``++finalize()++`` methods should be left exclusively to the JVM.
|
|
|
|
|
|
ifdef::env-github,rspecator-view[]
|
|
|
|
'''
|
|
== Implementation Specification
|
|
(visible only on this page)
|
|
|
|
include::../message.adoc[]
|
|
|
|
'''
|
|
== Comments And Links
|
|
(visible only on this page)
|
|
|
|
include::../comments-and-links.adoc[]
|
|
|
|
endif::env-github,rspecator-view[]
|