summaryrefslogtreecommitdiff
path: root/build2/list
blob: 179962cf2d5636c4152f6c01cfbc6e3736035b1b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
? Alternative/different syntax for operations on command line [idea]

  Something that doesn't require quoting and maybe even parens. Some ideas:

  configure[foo/@bar/]
  configure{foo/@bar/}
  configure: foo/@bar/ [.]    # flat spec?

  Would be nice to also make sure auto-completion is not inhibited.

- Value pack (comma-separated list of values) [idea]

  Could be used in function calls, attributes, config initializer. Question is
  whether comma will be treated as a separator in all contexts (which means it
  will have to be quoted in variable values, such as options). Perhaps only
  allow it in certain context (eval, attrubute)? Maybe also for certain
  variable types (multi-value variables, e.g., config init).

- Config reports for test, install, and dist modules [feature]

- Handle ^C [bug]

  Can we teach auto_rm to handle it? Also will need to use auto_rm in other
  places (compile, cli, etc). See what GNU make does.

? Paging build2 output [idea]

  Could be handy to be able to scroll back and forth and search as in less.
  But we somehow need to always show the tail. Also will have to detect if it
  is a redirect/non-tty (e.g., we don't want this in emacs).

? Colorized build2 output [idea]

  We could highlight the tool as well as braces, @, etc.

- Support for caching discovered configuration values [idea]

  The idea is to have depdb-based config.cache where we can cache things like
  compiler check results that are expensive to re-calculate on every run. The
  idea is to first save a checksum that determines if the cached value can be
  trusted.

- VC 15 support [feature 0.5.0]

  Need to install the preview, add detection, see if we can start testing with
  it. Wonder if any chance for cross-compile support.

- Get rid of string pools [quality parallel]

  They are most likely harmful because of the small object optimizations.