I'm not sure if this was intended by design or not, but why did you decide to put everything into one .scala file? I know Scala allows you to define multiple objects/classes in a file but it is pretty long and it would be pretty difficult to find what I'm looking for if I were to edit anything.
Otherwise, cool project. I too am also interested in graphs and Scala, so I'll be watching your project. Have you looked at flockDB from Twitter?
The one-file thing is because I'm new to the Scala build environment (although I have 2 years of Clojure and 2 years Ocaml + Haskell) environment. I was just delaying on that SBT/Maven question for as long as possible.
I generally split files around 500 lines, but for FP languages that may be a bit big.
Haven't looked at FlockDB. Twitter does a lot of cool stuff-- and they use Scala. I may consider applying if I decide to move out to CA.
Comments
I'm not sure if this was intended by design or not, but why did you decide to put everything into one .scala file? I know Scala allows you to define multiple objects/classes in a file but it is pretty long and it would be pretty difficult to find what I'm looking for if I were to edit anything.
Otherwise, cool project. I too am also interested in graphs and Scala, so I'll be watching your project. Have you looked at flockDB from Twitter?
The one-file thing is because I'm new to the Scala build environment (although I have 2 years of Clojure and 2 years Ocaml + Haskell) environment. I was just delaying on that SBT/Maven question for as long as possible.
I generally split files around 500 lines, but for FP languages that may be a bit big.
Haven't looked at FlockDB. Twitter does a lot of cool stuff-- and they use Scala. I may consider applying if I decide to move out to CA.