Setting package in Scala REPL












6















Is there a way in the Scala REPL to set the "active" package scope ? Say I have a package com.package with class A, I want to be able to type new A() instead of new com.package.A() without explicitly doing import com.package.A. There might be a number of other classes in that package I'm interested into and I don't want to polute my REPL's global namespace by doing import com.package._.



Even better, I'd like to define class A without typing its fully qualified name. Something like:



package com.package // do this once

class A
class B

val a = new A()
val b = new B()


I'm aware of the :paste -raw command, but that would require me to type package com.package for each block; I'm really looking for a stateful command to change the "current working package", if you will.










share|improve this question























  • So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?

    – VonC
    Aug 16 '14 at 19:37






  • 1





    there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...

    – gourlaysama
    Aug 16 '14 at 19:41













  • @VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.

    – gsimard
    Aug 16 '14 at 19:45











  • Ditto @gourlaysama The use case is testing existing classes with package-private access.

    – som-snytt
    Aug 18 '14 at 15:20











  • Possible duplicate of How to use members with default (package) or private access level in REPL?

    – Jacek Laskowski
    Oct 14 '15 at 9:26
















6















Is there a way in the Scala REPL to set the "active" package scope ? Say I have a package com.package with class A, I want to be able to type new A() instead of new com.package.A() without explicitly doing import com.package.A. There might be a number of other classes in that package I'm interested into and I don't want to polute my REPL's global namespace by doing import com.package._.



Even better, I'd like to define class A without typing its fully qualified name. Something like:



package com.package // do this once

class A
class B

val a = new A()
val b = new B()


I'm aware of the :paste -raw command, but that would require me to type package com.package for each block; I'm really looking for a stateful command to change the "current working package", if you will.










share|improve this question























  • So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?

    – VonC
    Aug 16 '14 at 19:37






  • 1





    there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...

    – gourlaysama
    Aug 16 '14 at 19:41













  • @VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.

    – gsimard
    Aug 16 '14 at 19:45











  • Ditto @gourlaysama The use case is testing existing classes with package-private access.

    – som-snytt
    Aug 18 '14 at 15:20











  • Possible duplicate of How to use members with default (package) or private access level in REPL?

    – Jacek Laskowski
    Oct 14 '15 at 9:26














6












6








6


2






Is there a way in the Scala REPL to set the "active" package scope ? Say I have a package com.package with class A, I want to be able to type new A() instead of new com.package.A() without explicitly doing import com.package.A. There might be a number of other classes in that package I'm interested into and I don't want to polute my REPL's global namespace by doing import com.package._.



Even better, I'd like to define class A without typing its fully qualified name. Something like:



package com.package // do this once

class A
class B

val a = new A()
val b = new B()


I'm aware of the :paste -raw command, but that would require me to type package com.package for each block; I'm really looking for a stateful command to change the "current working package", if you will.










share|improve this question














Is there a way in the Scala REPL to set the "active" package scope ? Say I have a package com.package with class A, I want to be able to type new A() instead of new com.package.A() without explicitly doing import com.package.A. There might be a number of other classes in that package I'm interested into and I don't want to polute my REPL's global namespace by doing import com.package._.



Even better, I'd like to define class A without typing its fully qualified name. Something like:



package com.package // do this once

class A
class B

val a = new A()
val b = new B()


I'm aware of the :paste -raw command, but that would require me to type package com.package for each block; I'm really looking for a stateful command to change the "current working package", if you will.







scala read-eval-print-loop






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Aug 16 '14 at 19:30









gsimardgsimard

381422




381422













  • So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?

    – VonC
    Aug 16 '14 at 19:37






  • 1





    there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...

    – gourlaysama
    Aug 16 '14 at 19:41













  • @VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.

    – gsimard
    Aug 16 '14 at 19:45











  • Ditto @gourlaysama The use case is testing existing classes with package-private access.

    – som-snytt
    Aug 18 '14 at 15:20











  • Possible duplicate of How to use members with default (package) or private access level in REPL?

    – Jacek Laskowski
    Oct 14 '15 at 9:26



















  • So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?

    – VonC
    Aug 16 '14 at 19:37






  • 1





    there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...

    – gourlaysama
    Aug 16 '14 at 19:41













  • @VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.

    – gsimard
    Aug 16 '14 at 19:45











  • Ditto @gourlaysama The use case is testing existing classes with package-private access.

    – som-snytt
    Aug 18 '14 at 15:20











  • Possible duplicate of How to use members with default (package) or private access level in REPL?

    – Jacek Laskowski
    Oct 14 '15 at 9:26

















So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?

– VonC
Aug 16 '14 at 19:37





So, I guess stackoverflow.com/a/18510229/6309 wouldn't be helpful either?

– VonC
Aug 16 '14 at 19:37




1




1





there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...

– gourlaysama
Aug 16 '14 at 19:41







there is currently no support for that because packages are actually used in the internals of the REPL (classes defined in the REPL don't actually live in the root package), but that would make an interesting feature request...

– gourlaysama
Aug 16 '14 at 19:41















@VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.

– gsimard
Aug 16 '14 at 19:45





@VonC: No, this would not allow me to define new classes without a fully qualified name, as per my question.

– gsimard
Aug 16 '14 at 19:45













Ditto @gourlaysama The use case is testing existing classes with package-private access.

– som-snytt
Aug 18 '14 at 15:20





Ditto @gourlaysama The use case is testing existing classes with package-private access.

– som-snytt
Aug 18 '14 at 15:20













Possible duplicate of How to use members with default (package) or private access level in REPL?

– Jacek Laskowski
Oct 14 '15 at 9:26





Possible duplicate of How to use members with default (package) or private access level in REPL?

– Jacek Laskowski
Oct 14 '15 at 9:26












1 Answer
1






active

oldest

votes


















7














Simply put, you cannot.



Each command in the scala REPL is wrapped into a newly generated package, as explained here.



Also, there was a ticket asking package { } support in the REPL, but it was dismissed as :paste -raw was considered enough for the purpose.






share|improve this answer


























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f25343217%2fsetting-package-in-scala-repl%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    7














    Simply put, you cannot.



    Each command in the scala REPL is wrapped into a newly generated package, as explained here.



    Also, there was a ticket asking package { } support in the REPL, but it was dismissed as :paste -raw was considered enough for the purpose.






    share|improve this answer






























      7














      Simply put, you cannot.



      Each command in the scala REPL is wrapped into a newly generated package, as explained here.



      Also, there was a ticket asking package { } support in the REPL, but it was dismissed as :paste -raw was considered enough for the purpose.






      share|improve this answer




























        7












        7








        7







        Simply put, you cannot.



        Each command in the scala REPL is wrapped into a newly generated package, as explained here.



        Also, there was a ticket asking package { } support in the REPL, but it was dismissed as :paste -raw was considered enough for the purpose.






        share|improve this answer















        Simply put, you cannot.



        Each command in the scala REPL is wrapped into a newly generated package, as explained here.



        Also, there was a ticket asking package { } support in the REPL, but it was dismissed as :paste -raw was considered enough for the purpose.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited May 23 '17 at 12:10









        Community

        11




        11










        answered Aug 16 '14 at 19:45









        Gabriele PetronellaGabriele Petronella

        92.2k18181213




        92.2k18181213
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f25343217%2fsetting-package-in-scala-repl%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            鏡平學校

            ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

            Why https connections are so slow when debugging (stepping over) in Java?