pretty printing doesn't put enough EOLs

[yegor256]

related to #515

I'm getting this output:

...
method-params ↦ Φ.jeo.params, annotations ↦ Φ.org.eolang.seq0, φ ↦ Φ.org.eolang.seq3 (
  α0 ↦ ξ.aload-BD64, α1 ↦ ξ.invokespecial-BD66, α2 ↦ ξ.return-BD68
),
trycatchblocks-object@init@ ↦ Φ.org.eolang.seq0, local-variable-table ↦ Φ.org.eolang.seq0, aload-BD64 ↦ Φ.jeo.opcode (
  α0 ↦ Φ.jeo.int (
    α0 ↦ Φ.org.eolang.bytes (
      Δ ⤍ 00-00-00-00-00-00-00-19
    )
  ),
  α1 ↦ Φ.jeo.int (
    α0 ↦ Φ.org.eolang.bytes (
      Δ ⤍ 00-00-00-00-00-00-00-00
    )
  )
),
...

Obviously, a better formatting would be:

...
method-params ↦ Φ.jeo.params, 
annotations ↦ Φ.org.eolang.seq0, 
φ ↦ Φ.org.eolang.seq3 (
  α0 ↦ ξ.aload-BD64, 
  α1 ↦ ξ.invokespecial-BD66, 
  α2 ↦ ξ.return-BD68
),
trycatchblocks-object@init@ ↦ Φ.org.eolang.seq0, 
local-variable-table ↦ Φ.org.eolang.seq0, 
aload-BD64 ↦ Φ.jeo.opcode (
  α0 ↦ Φ.jeo.int (
    α0 ↦ Φ.org.eolang.bytes (
      Δ ⤍ 00-00-00-00-00-00-00-19
    )
  ),
  α1 ↦ Φ.jeo.int (
    α0 ↦ Φ.org.eolang.bytes (
      Δ ⤍ 00-00-00-00-00-00-00-00
    )
  )
),

[yegor256]

@deemp @fizruk please, check

[yegor256]

@fizruk here is a more simple example:

$ cat bar.phi
{⟦ m ↦ ⟦ x ↦ ξ.t, φ ↦ ⟦ t ↦ ⟦⟧ ⟧ ⟧.x ⟧}
$ eo-phi-normalizer rewrite -s bar.phi
{
  ⟦
    m ↦ ⟦
      ρ ↦ ⟦
        t ↦ ⟦ ⟧, ρ ↦ ⟦
          x ↦ ξ.t, φ ↦ ⟦
            t ↦ ⟦ ⟧
          ⟧
        ⟧
      ⟧
    ⟧
  ⟧
}

Obviously, the formatting is wrong.

[yegor256]

@deemp let's close it when the problem is solved on my side, in a new release

[deemp]

@yegor256, we've released v2.2.0 that should resolve this issue. Please check

[0crat]

@yegor256 Thank you for your submission! Unfortunately, it wasn't accepted by the team. As per our policy, this results in a -16 point penalty. Your current balance is now -78. Don't be discouraged, though! Your efforts to improve our project's quality are valuable. Keep reporting bugs and suggesting enhancements, but try to be more thorough next time. Remember, bugs are welcome when they help us grow!

[yegor256]

@deemp this problem is gone