Different formats of one-liners

gistfile1.scala

  // Ugly one-liner: type is in the middle of the line, implementation takes less than half a line
  // Pain!
  implicit class RichSsWorkbook(wb: Workbook) {
    def apply(i: Int): Sheet = wb.getSheetAt(i)

    def bytes: Array[Byte] = {
      val baos = new ByteArrayOutputStream
      wb.write(baos)
      baos.toByteArray
    }
  }
  
  // Beautiful, structured multi-liner
  // You can see the type ane implementation in one look!
  // A pleasure to watch
  implicit class RichSsWorkbook(wb: Workbook) {
    def apply(i: Int): Sheet =
      wb.getSheetAt(i)

    def bytes: Array[Byte] = {
      val baos = new ByteArrayOutputStream
      wb.write(baos)
      baos.toByteArray
    }
  }

  // These one-liners are okay though - no return types and they are grouped together
  implicit class RichSsWorkbook(wb: Workbook) {
    def test1(i: Int) = wb.getSheetAt(i)
    
    def otherTest2(i: Int) = wb.getSheetAt(i)
    
    def evenTesterTest3(i: Int) = wb.getSheetAt(i)
  }