{"action":"opened","issue":{"url":"https://api.github.com/repos/uniphil/results/issues/88","repository_url":"https://api.github.com/repos/uniphil/results","labels_url":"https://api.github.com/repos/uniphil/results/issues/88/labels{/name}","comments_url":"https://api.github.com/repos/uniphil/results/issues/88/comments","events_url":"https://api.github.com/repos/uniphil/results/issues/88/events","html_url":"https://github.com/uniphil/results/issues/88","id":147525397,"number":88,"title":"Unwrapping constructor gets weird","user":{"login":"uniphil","id":205128,"avatar_url":"https://avatars.githubusercontent.com/u/205128?v=3","gravatar_id":"","url":"https://api.github.com/users/uniphil","html_url":"https://github.com/uniphil","followers_url":"https://api.github.com/users/uniphil/followers","following_url":"https://api.github.com/users/uniphil/following{/other_user}","gists_url":"https://api.github.com/users/uniphil/gists{/gist_id}","starred_url":"https://api.github.com/users/uniphil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/uniphil/subscriptions","organizations_url":"https://api.github.com/users/uniphil/orgs","repos_url":"https://api.github.com/users/uniphil/repos","events_url":"https://api.github.com/users/uniphil/events{/privacy}","received_events_url":"https://api.github.com/users/uniphil/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-11T19:14:50Z","updated_at":"2016-04-11T19:14:50Z","closed_at":null,"body":"`Maybe.undefined(Maybe.None()) => Maybe.None()`, not `Maybe.Some(Maybe.None())`.\r\n\r\nI mean, if I wrote the second, it would also become `Maybe.None()` because of the unwrapping constructor, so this makes sense and does what it's supposed to, but it makes it weird when trying to do something like check for an optional parameter that is a Maybe to give it a default case. "}}