{"action":"created","issue":{"url":"https://api.github.com/repos/JuliaLang/julia/issues/10333","labels_url":"https://api.github.com/repos/JuliaLang/julia/issues/10333/labels{/name}","comments_url":"https://api.github.com/repos/JuliaLang/julia/issues/10333/comments","events_url":"https://api.github.com/repos/JuliaLang/julia/issues/10333/events","html_url":"https://github.com/JuliaLang/julia/issues/10333","id":59012462,"number":10333,"title":"Move DArrays from Base","user":{"login":"ViralBShah","id":744411,"avatar_url":"https://avatars.githubusercontent.com/u/744411?v=3","gravatar_id":"","url":"https://api.github.com/users/ViralBShah","html_url":"https://github.com/ViralBShah","followers_url":"https://api.github.com/users/ViralBShah/followers","following_url":"https://api.github.com/users/ViralBShah/following{/other_user}","gists_url":"https://api.github.com/users/ViralBShah/gists{/gist_id}","starred_url":"https://api.github.com/users/ViralBShah/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ViralBShah/subscriptions","organizations_url":"https://api.github.com/users/ViralBShah/orgs","repos_url":"https://api.github.com/users/ViralBShah/repos","events_url":"https://api.github.com/users/ViralBShah/events{/privacy}","received_events_url":"https://api.github.com/users/ViralBShah/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/JuliaLang/julia/labels/parallel","name":"parallel","color":"f7e102"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":18,"created_at":"2015-02-26T03:28:41Z","updated_at":"2015-03-02T18:45:57Z","closed_at":"2015-02-27T23:02:37Z","body":"We need a ton of functionality to be developed on DArrays, and perhaps even experimentation with layouts and such. I feel it is best to move the DArray functionality out of Base into the JuliaParallel organization (https://github.com/JuliaParallel) and develop it there."},"comment":{"url":"https://api.github.com/repos/JuliaLang/julia/issues/comments/76776950","html_url":"https://github.com/JuliaLang/julia/issues/10333#issuecomment-76776950","issue_url":"https://api.github.com/repos/JuliaLang/julia/issues/10333","id":76776950,"user":{"login":"jiahao","id":1732,"avatar_url":"https://avatars.githubusercontent.com/u/1732?v=3","gravatar_id":"","url":"https://api.github.com/users/jiahao","html_url":"https://github.com/jiahao","followers_url":"https://api.github.com/users/jiahao/followers","following_url":"https://api.github.com/users/jiahao/following{/other_user}","gists_url":"https://api.github.com/users/jiahao/gists{/gist_id}","starred_url":"https://api.github.com/users/jiahao/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jiahao/subscriptions","organizations_url":"https://api.github.com/users/jiahao/orgs","repos_url":"https://api.github.com/users/jiahao/repos","events_url":"https://api.github.com/users/jiahao/events{/privacy}","received_events_url":"https://api.github.com/users/jiahao/received_events","type":"User","site_admin":false},"created_at":"2015-03-02T18:45:57Z","updated_at":"2015-03-02T18:45:57Z","body":"> Here code was just deleted, the upside is in modularity and development constraints of being inside vs outside of base but there's no urgency on those points.\r\n\r\nUnlike the `Base.Graphics` removal,  at this point we do have a critical mass of applications waiting to be written (like parallel linear algebra) _and_ the labor to do it (those cc'ed in the OP) _and_ lots of potentially breaking changes (like user-customizable transports) to try out.\r\n\r\n> Getting various other packages to use the new Graphics version was done quickly enough, but in retrospect it should not have used the same name as the base module.\r\n\r\nNo, the problems with `Graphics.jl` are not so simple as to be solved by renaming the module. Please read what I wrote above about importing conflicting definitions more carefully. The current situation is metastable and will collapse the moment a breaking change in `Graphics.jl` is made.\r\n\r\n> Conditional loading in Compat? If the module in main exists, do nothing, else load the external module...\r\n\r\nI don't see how `Compat.jl` will solve the problem of breaking backward compatibility. At best it can only offer the kind of feature freeze which can also be expressed by putting `julia 0.4-dev+1234` in the `REQUIRE` file of the newly externalized package. Furthermore, it appears that `Compat` macros do not compose with macros or other applications requiring compile-time code generation. (I couldn't figure out how to use `Compat` in an expression like `BinDeps.@install [:lib => :symbol]`. `BinDeps.@install @compat Dict(:lib => :symbol)` does not work, but admittedly it's not my highest priority to figure out how to fix this.)"}}