juan_gandhi: (Default)

У меня есть набор тестов с топосной логикой; там расчеты довольно тяжелые; часа 2 с лишним уходило.

Переключился сейчас со скалы 2.12 на скалу 2.13, и jvm с 7 на 11.

В два раза быстрее. 

juan_gandhi: (Default)
I have a class named `Category`, and it has a member `type Object`, so far so good.
But then in one place the compiled code (or JVM) does not understand that it is not `java.lang.Object`, and tries to find a method that takes `java.lang.Object` while the methods I have takes some path-dependent type named `Object`.

So, to avoid this stupidity with JVM (or scala compiler), I have to find an alternative name. Can't figure out what it can be. Just `O` (and `A` for arrows?)

I'm in panic.

juan_gandhi: (VP)
Seems like scala people look down at exceptions... but see. The difference between an error message and an exception is that an exception tells you where the error happened. I actually use it in pretty unusual places, like this:
def jsREPL(implicit prompt:String = "type your js") {
  val here = Thread.currentThread().getStackTrace()(3)
  println(s"$prompt [${here.getFileName}:${here.getLineNumber}]: ")
  Source.fromInputStream(System.in).getLines.takeWhile(!_.isEmpty) foreach {
    s => println(tryOr(runJS(s), (_:Exception).getMessage))
  }


What I want to say: if we, in Scala, had a habit of passing around exceptions, instead of plain text, it would be pretty helpful.

Thinking about it.

Profile

juan_gandhi: (Default)
Juan-Carlos Gandhi

August 2025

S M T W T F S
      12
3456789
10 11 12 13141516
17181920212223
24252627282930
31      

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Aug. 13th, 2025 11:31 pm
Powered by Dreamwidth Studios