| object Oid { | |
| def unapply(s: String): Option[ObjectId] = { | |
| if(ObjectId.isValid(s)) Some(new ObjectId(s)) | |
| else None | |
| } | |
| } | |
| … | |
| def intent = { |
| scala> MongoDBObject("foo" -> None).getAs[String]("foo") | |
| res0: Option[String] = Some(None) | |
| scala> MongoDBObject("foo" -> null).getAs[String]("foo") | |
| res0: Option[String] = None |
| function flatten(list) { | |
| return _.reduce(list, function(acc, item) { | |
| return acc.concat(item); | |
| }, []); | |
| } | |
| function flatMap(list, func, context) { | |
| return flatten(_.map(list, func, context)); | |
| } |
| @(elements: helper.FieldElements) | |
| @************************************************** | |
| * Generate input according twitter bootsrap rules * | |
| **************************************************@ | |
| <div class="control-group@if(elements.hasErrors) {" errors"}"> | |
| <label for="@elements.id" class="control-label">@elements.label</label> | |
| <div class="controls"> | |
| @elements.input | |
| <span class="help-inline">@((elements.errors ++ elements.infos).mkString(", "))</span> |
| def method(a: Any): String = a match { | |
| case i: Int => "Int" | |
| case s: String => "String" | |
| case _ => "Other" | |
| } |
| myWorkspaces = zipWith (++) | |
| (map show [1..12]) $ | |
| map (":"++) | |
| [ "Web" | |
| , "Code" | |
| , "SSH" | |
| , "Social" | |
| , "Email" | |
| , "Music" | |
| , "Video" |
| scala> Some("yolo").fold(Nil)(List(_)) | |
| <console>:8: error: type mismatch; | |
| found : List[String] | |
| required: scala.collection.immutable.Nil.type | |
| Some("yolo").fold(Nil)(List(_)) | |
| ^ | |
| scala> Some("yolo").map(List(_)).getOrElse(Nil) | |
| res1: List[String] = List(yolo) |
| Tikhon Jelvis, consistency is all I ask | |
| Votes by Jed Wesley-Smith, Scott Danzig, Gregory Popovitch, Toby Thain, and 111 more. | |
| Most modern and well-featured? Hah! It's hard to tell it wasn't design 30 years ago. Go completely ignores most recent advances in programming languages in order to seem more similar to C. Charming. | |
| Yes, there are drawbacks you're not seeing. But, more importantly, there are better alternatives you're ignoring. While some of the problems with Go are certainly actively detrimental, the bigger story is opportunity cost: you're missing out on some more capable, more expressive and safer languages. | |
| So lets take your question in two parts: Go's drawbacks and then better alternatives. | |
| Drawbacks |
Gist does not let me put directories names in file names, so make sure to put:
assets-Gruntfile.js in assets/Gruntfile.jsassets-package.json in assets/package.jsonproject-Grunt.scala in project/Grunt.scalaproject-JavaScriptBuild.scala in project/JavaSCriptBuild.scalaThe goal is to let grunt handle everything in the assets directory.
I hereby claim:
To claim this, I am signing this object: