{"action":"opened","issue":{"url":"https://api.github.com/repos/uklimaschewski/EvalEx/issues/171","repository_url":"https://api.github.com/repos/uklimaschewski/EvalEx","labels_url":"https://api.github.com/repos/uklimaschewski/EvalEx/issues/171/labels{/name}","comments_url":"https://api.github.com/repos/uklimaschewski/EvalEx/issues/171/comments","events_url":"https://api.github.com/repos/uklimaschewski/EvalEx/issues/171/events","html_url":"https://github.com/uklimaschewski/EvalEx/issues/171","id":328813961,"node_id":"MDU6SXNzdWUzMjg4MTM5NjE=","number":171,"title":"MathContext of Expression is not available to functions and operators.","user":{"login":"RobertZenz","id":611377,"node_id":"MDQ6VXNlcjYxMTM3Nw==","avatar_url":"https://avatars0.githubusercontent.com/u/611377?v=4","gravatar_id":"","url":"https://api.github.com/users/RobertZenz","html_url":"https://github.com/RobertZenz","followers_url":"https://api.github.com/users/RobertZenz/followers","following_url":"https://api.github.com/users/RobertZenz/following{/other_user}","gists_url":"https://api.github.com/users/RobertZenz/gists{/gist_id}","starred_url":"https://api.github.com/users/RobertZenz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RobertZenz/subscriptions","organizations_url":"https://api.github.com/users/RobertZenz/orgs","repos_url":"https://api.github.com/users/RobertZenz/repos","events_url":"https://api.github.com/users/RobertZenz/events{/privacy}","received_events_url":"https://api.github.com/users/RobertZenz/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-03T09:32:43Z","updated_at":"2018-06-03T09:32:43Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"I've just realized that with the implementation of #144 and #155 a small hole in the API has been opened. For example, a `LazyFunction` implementation defined outside the `Expression` does not have access to the `MathContext` used by the `Expression`.\r\n\r\nAdding a getter for the `MathContext` on the `Expression` does not solve that (but it would still be nice to have). Ideally, the `MathContext` would be passed to these implementations, but I'm not very fond of that as it would require to break the API. Alternatively one could make sure that all parameters passed to functions have the correct `MathContext`, so that a function can rely on that. I'm not sure whether that is already happening, but I guess not (as `BigDecimals` can be directly set as parameters)."}}
{"actor":{"display_login":"RobertZenz"}}