kotct / dot

75%

master: 75%

LAST BUILD ON BRANCH fix-config-compilation-issues

branch: fix-config-compilation-issues

CHANGE BRANCH

x

Reset

• fix-config-compilation-issues
• 0.3-pre
• add-force-load-to-kotct/switch-to-theme
• avy
• c
• ci-disable-emacs-25.3
• clean-up-rakefile
• code-of-conduct
• code-style
• coverage-reporting
• csharp
• darwin-use-sh
• display-line-numbers-mode
• emacs-27.1
• emergency-load
• evm
• feature/magit-completion
• fish-support
• fix-125
• fix-141
• fix-144
• fix-147
• fix-repositories
• font-function-fault-tolerance
• gh-actions
• git-modes
• go-mode
• goto-chg
• helm
• hotfix/85-fix-ci-by-requiring-cl-at-compile
• interactive-git
• ivy
• kill-emacs
• magit-completion
• master
• mjs-web
• no-slack
• packup-fixes
• packup-ui
• prefer-utf-8
• recentf-fix
• release/v0.2.0
• remove-25.3
• remove-indentation-configuration
• remove-unnecessary-call-to-package-initialize
• require-package
• sh-indent
• stable
• startup-print-gcs
• test-current-emacs-versions
• tex
• theme-hack
• tramp-default
• travis-upgrade-emacs-26.3
• update-emacs
• update-package-archive-priorities
• v0.2.0
• yaml-mode
• yaml-whitespace

Build # 344

Build Type

push

travis-ci

Committed by rye

Commit Message

init: Move most requires into eval-when-compile blocks

Symbols typically fall into two categories: those registered explicitly
with `autoload` (e.g. via `;;;###autoload` and such), and those referred
to via the `register-definition-prefixes` function which helps to inform
autoloading.  It seems that those in the latter category will sometimes
fail to be detected by the system.  A third---and quite pesky---category
is those which do not have any autoload definitions prepared for them,
nor any prefixes hinting where autoload can hunt for their definitions.

Now, all external require statements are performed according to a
somewhat straightforward set of rules:

- If a (require) *is* directly used at evaluation time, it must be
  required immediately.

- If a (require) is not needed at evaluation time, (i.e. the file being
  evaluated never refers to any symbols present there) then the require
  can safely be moved into an eval-when-compile.

In some cases, moving a require into an eval-when-compile makes the
compiler a bit concerned, so manual (autoload) invocations seem to
effectively inform the compiler that yes, indeed, symbols are to be
autoloaded.

Signed-off-by: Kristofer Rye <kristofer.rye@gmail.com>

Run Details

18 of 24 relevant lines covered (75.0%)

1.58 hits per line