From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-3.8 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id DD8B01F453 for ; Fri, 8 Feb 2019 00:38:43 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id F19D211911E; Fri, 8 Feb 2019 09:38:39 +0900 (JST) Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by neon.ruby-lang.org (Postfix) with ESMTPS id 67F4A11911A for ; Fri, 8 Feb 2019 09:38:36 +0900 (JST) Received: by filter0132p3las1.sendgrid.net with SMTP id filter0132p3las1-10096-5C5CCF8B-C 2019-02-08 00:38:35.226000917 +0000 UTC m=+193332.843373354 Received: from herokuapp.com (ec2-54-226-126-161.compute-1.amazonaws.com [54.226.126.161]) by ismtpd0039p1iad2.sendgrid.net (SG) with ESMTP id jgsjRTzMQlKNEVqdpgqOcg for ; Fri, 08 Feb 2019 00:38:35.089 +0000 (UTC) Date: Fri, 08 Feb 2019 00:38:35 +0000 (UTC) From: akr@fsij.org To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 66938 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 15592 X-Redmine-Issue-Author: akr X-Redmine-Sender: akr X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS5u46zXLKoWjpihwlHDo1Uo0R4JN1WpNRtrHp q5clZb0aVeJQ6dPgJSoCjDWvwQ13W9rP6+vcs3ZSB73oJWs67SBr1YKhdlLlqDj3snYlfhRbhtyyG5 +hEW3SU8Gtm6ZX3DAvl/YMVbwq00IhRegide X-ML-Name: ruby-core X-Mail-Count: 91485 Subject: [ruby-core:91485] [Ruby trunk Feature#15592] mode that "autoload" behaves "require" immediately X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #15592 has been updated by akr (Akira Tanaka). Eregon (Benoit Daloze) wrote: > An idea: a simple interface could be `SomeNamespaceToBeDefined.eager_load_autoloads`, which is then invoked by the user after the application is "loaded". Great. I feel it is better than my idea. ---------------------------------------- Feature #15592: mode that "autoload" behaves "require" immediately https://bugs.ruby-lang.org/issues/15592#change-76744 * Author: akr (Akira Tanaka) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- How about a feature to switch "autoload" behavior to "require" immediately. autoload is a feature for lazy loading. matz dislikes autoload as [Feature #5653]. I heard that he dislikes class (and other) definitions at arbitrary timing. I agree that eager loading is safer than lazy loading. However, lazy loading realize shorter loading time and it makes development cycle shorter. It is more important for larger applications as Eregon said in https://bugs.ruby-lang.org/issues/5653#note-39 . It is especially important when library loading causes I/O (code generation from DB schema). These two, safety of eager loading and easier development of lazy loading, conflicts. But if we can distinguish production mode and development mode, we can enjoy both benefits. So, I propose a feature to select autoload behavior from two modes: - autoload behaves as lazy loading as now in development mode - autoload behaves as eager loading (immediately invokes "require") in production mode. There are several idea to switch the mode: - $AUTOLOAD_MODE = :eager or :lazy - RubyVM.autoload_mode = :eager or :lazy - ObjectSpace.autoload_mode = :eager or lazy I'm not sure there is a good enough one in above list, though. -- https://bugs.ruby-lang.org/