Should * or i be used for footer information?

[DavisVaughan]

With #617 we now use bullets for separating footer information like

Did we ever consider using i for this instead? In most of our error / warning messaging, we now use i to convey a general "info bullet" and it seems like this might fall in that category.

@lionel- do you have any thoughts about i vs * here?

[lionel-]

I think so too.

By the way, did we consider standardising the header to use the conventional angular brackets?

[krlmlr]

Like this?

# A tibble: [2,196 x 11]

[lionel-]

Like

#> <tibble [2,196 x 11]>

I think tibble is about the only place where we use a # header?

[krlmlr]

How would we print a multiline header?

[lionel-]

I think we'd use the conventional approach and wouldn't have a multiline header? More information could be displayed in bullets instead? But I don't know in what cases tibble uses multiline headers.

[krlmlr]

In subclasses of "tbl":

dbplyr::memdb_frame(a = 1)
#> # Source:   table<dbplyr_001> [1 x 1]
#> # Database: sqlite 3.40.1 [:memory:]
#>       a
#>   <dbl>
#> 1     1

^{Created on 2023-02-16 with reprex v2.0.2}

[lionel-]

Following for instance the rlang_error formatting, this could be:

#> <table<dbplyr_001> [1 x 1]>
#> Database: sqlite 3.40.1 [:memory:]
#>       a
#>   <dbl>
#> 1     1

[DavisVaughan]

@hadley requested we keep it as # back here #542 (comment)

Changing it would probably be fairly disruptive to subclass authors who have provided extra # lines in their headers, like tsibble and data base backends

[krlmlr]

Closing, please reopen/comment if this was bad judgment.

[lionel-]

No info bullets then?

[krlmlr]

Right, we can try info bullets.