enso/docs/debugger/mixed-debugging.md

# Debugging Enso and Java Code at Once

Desribed at [Runtime Debugging](runtime-debugging.md).
Invoke all Enso benchmarks via JMH (#7101) # Important Notes #### The Plot - there used to be two kinds of benchmarks: in Java and in Enso - those in Java got quite a good treatment - there even are results updated daily: https://enso-org.github.io/engine-benchmark-results/ - the benchmarks written in Enso used to be 2nd class citizen #### The Revelation This PR has the potential to fix it all! - It designs new [Bench API](https://github.com/enso-org/enso/pull/7101/commits/88fd6fb9888d939c2d9745a7397f6e87dec4fa4d) ready for non-batch execution - It allows for _single benchmark in a dedicated JVM_ execution - It provides a simple way to wrap such an Enso benchmark as a Java benchmark - thus the results of Enso and Java benchmarks are [now unified](https://github.com/enso-org/enso/pull/7101#discussion_r1257504440) Long live _single benchmarking infrastructure for Java and Enso_! 2023-08-07 15:39:01 +03:00			`# Debugging Enso and Java Code at Once`

Unifying debugging information (#8370) 2023-11-27 11:37:51 +03:00			`Desribed at [Runtime Debugging](runtime-debugging.md).`