juan_gandhi | Entries tagged with common sense

  def tryOr[T](message: String)(action: => T) = {
    try {
      Some(action)
    } catch {
      case e: Throwable => {
        Log.error(message, e)
        None
      }
    }
  }

using like

tryOr("Oi-vei, could not find...") { database.findUserNamed("Captain Nemo") }

Could use Either as well, I don't know.
Gradually morphing from Java.

Spent like an hour trying to figure out how to serialize to json the object I build from json (to pass around the network); then it occurred to me it's immutable. Why not keep the source, eh. Like class files, they'd be happier if they just had the source code accompanying them naturally somewhere, eh.

So there. I just store the object's own source. Neat, eh.

Why are defs in the component definition better as the way to obtain the dependency? Because if you use a val, all implementations are locked and have to provide a single dependency instance (a constant). With a method, you can return different values on each invocation. For example, in a web environment, this is a great way to implement scoping! The method can read from the request or session state. Of course, it is still possible to provide a singleton. Or a new instance of the dependency on each invocation.

S	M	T	W	T	F	S
				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30	31

Observations

Views from Souths

Entries tagged with common sense

getting rid of fucking exceptions

serializing an immutable object

using cake pattern for di in scala

Profile

May 2025

Syndicate

Most Popular Tags

Page Summary

Active Entries

Style Credit

Expand Cut Tags