| 20 Jul 2023 |
 infinisil | pennae: I did apparently! Although there's some special handling for the first line | 18:45:29 |
 @pennae:matrix.eno.space | not sure the first line should be handled specially | 18:50:28 |
| @pennae:matrix.eno.space | do you have an example where dedent would misbehave? | 18:50:39 |
| infinisil | pennae: For cases like
/* This is some docs
For a function
*/
| 18:50:55 |
| @pennae:matrix.eno.space | that would be handled by dedent(...).trim() | 18:51:36 |
| infinisil | Also:
/*
Type: foo :: {
x :: Int;
y :: Bool;
}
*/
| 18:52:00 |
| infinisil | In reply to @pennae:matrix.eno.space
that would be handled by dedent(...).trim() Ahh 🤔 | 18:52:19 |
| infinisil | Yeah lemme try dedent then :) | 18:52:30 |
| @pennae:matrix.eno.space | In reply to @infinisil:matrix.org
Also:
/*
Type: foo :: {
x :: Int;
y :: Bool;
}
*/
that too? dedent ignores the first line, the rest is dedented by two spaces | 18:52:31 |
| infinisil | pennae: Are you sure? The docs don't mention anything of that | 18:53:43 |
| infinisil | Anyways, I'll just try it out | 18:53:47 |
| infinisil | Yeah it doesn't treat the first line differently | 19:01:12 |
| infinisil | pennae: Was able to use it though, thanks for the suggestion, PR updated | 19:14:48 |
| @pennae:matrix.eno.space | we do have an overabundance of doxygen-style comments in lib docs, we can't help but notice :D | 19:16:54 |
| 21 Jul 2023 |
|  kookie changed their display name from kookie (offline) to kookie. | 07:59:26 |
|  Domen Kožar changed their profile picture. | 12:30:59 |
 asymmetric | This RFC proposing documenting support tiers got merged, but I can't find any mention of support tiers in nixpkgs+nixos manuals. Am I looking in the wrong place? | 16:41:50 |
| infinisil | asymmetric: RFC 46 introduced the support tiers: https://github.com/NixOS/rfcs/pull/46 | 16:43:48 |
| infinisil | Maybe it was never properly implemented by documenting it anywhere.. | 16:44:00 |
| infinisil | (other than the RFC) | 16:44:04 |
| asymmetric | yeah, that's what i'm thinking.. ☹️ | 16:44:26 |
| asymmetric | it's kinda suprising how sometimes RFC end up merged but not implemented /rant | 16:44:52 |
| asymmetric | * it's kinda suprising how sometimes RFCs end up merged but not implemented /rant | 16:44:57 |
| asymmetric | this seems to be the last state of the conversation re: documenting the tiers: https://github.com/NixOS/rfcs/pull/46#issuecomment-669019148 | 16:46:37 |
| infinisil | Only like 3 years too late 🙃 | 16:47:15 |
 toonn | asymmetric: When I tried getting something started (https://github.com/NixOS/nixpkgs/pull/143732) there was not much motivation to discuss past "these strings aren't informative enough." | 22:21:45 |
 raitobezarius | I think implementing directly | 22:36:30 |
| raitobezarius |
I'm not sure that lib/systems/supported.nix contains sufficient information to serve as the platform tier list. This file is just the system doubles, and the support tier needs to take into account libc (musl/glibc), static/dynamic linking, gcc/clang, ABI, etc. If anything I think lib/systems/supported.nix would be autogenerated from the platform list, rather than the other way around.
| 22:36:31 |
| raitobezarius | *
I'm not sure that lib/systems/supported.nix contains sufficient information to serve as the platform tier list. This file is just the system doubles, and the support tier needs to take into account libc (musl/glibc), static/dynamic linking, gcc/clang, ABI, etc. If anything I think lib/systems/supported.nix would be autogenerated from the platform list, rather than the other way around.
| 22:36:33 |
| raitobezarius | would probably fly | 22:36:36 |
