{"action":"closed","issue":{"url":"https://api.github.com/repos/aepsil0n/carboxyl/issues/61","labels_url":"https://api.github.com/repos/aepsil0n/carboxyl/issues/61/labels{/name}","comments_url":"https://api.github.com/repos/aepsil0n/carboxyl/issues/61/comments","events_url":"https://api.github.com/repos/aepsil0n/carboxyl/issues/61/events","html_url":"https://github.com/aepsil0n/carboxyl/issues/61","id":75565858,"number":61,"title":"Revise `scan_mut`","user":{"login":"aepsil0n","id":3098430,"avatar_url":"https://avatars.githubusercontent.com/u/3098430?v=3","gravatar_id":"","url":"https://api.github.com/users/aepsil0n","html_url":"https://github.com/aepsil0n","followers_url":"https://api.github.com/users/aepsil0n/followers","following_url":"https://api.github.com/users/aepsil0n/following{/other_user}","gists_url":"https://api.github.com/users/aepsil0n/gists{/gist_id}","starred_url":"https://api.github.com/users/aepsil0n/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aepsil0n/subscriptions","organizations_url":"https://api.github.com/users/aepsil0n/orgs","repos_url":"https://api.github.com/users/aepsil0n/repos","events_url":"https://api.github.com/users/aepsil0n/events{/privacy}","received_events_url":"https://api.github.com/users/aepsil0n/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/aepsil0n/carboxyl/labels/bug","name":"bug","color":"fc2929"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-12T11:17:30Z","updated_at":"2015-05-12T13:39:59Z","closed_at":"2015-05-12T13:39:59Z","body":"In its current state `scan_mut` does not work particularly well, as it has subtly different semantics and allows one to side-step the abstraction provided by functional reactive programming, when used incorrectly. This must be fixed.\r\n\r\nThe concrete issue: If one propagates the result of `scan_mut` through further streams and signals, it will always reflect the status quo, as it remains a reference to the very same memory location. A possible solution would be to disallow this propagation by providing a separate interface with by-ref semantics for this kind of signal without exposing the underlying memory model."}}