3 Matching Annotations
  1. Jun 2023
  2. stackoverflow.com stackoverflow.com
    Private vs Protected - Visibility Good-Practice Concern
    1
    1. TylerRick 19 Jun 2023
      Have you ever: Been disappointed, surprised or hurt by a library etc. that had a bug that could have been fixed with inheritance and few lines of code, but due to private / final methods and classes were forced to wait for an official patch that might never come? I have. Wanted to use a library for a slightly different use case than was imagined by the authors but were unable to do so because of private / final methods and classes? I have.
      surprising disappointing good point +0.9 annotation meta: may need new tag well-intentioned protections causing pain or overly complicated workarounds can't think of everything only supporting some/specific/limited use cases
    Visit annotations in context

    Tags

    Annotators

    URL

    stackoverflow.com/questions/8353272/private-vs-protected-visibility-good-practice-concern
  3. Dec 2020
  4. github.com github.com
    CommonMark compliance · Discussion #1202 · markedjs/marked
    1
    1. TylerRick 09 Dec 2020
      What pain point are you perceiving?
      pain point issue template
    Visit annotations in context

    Tags

    Annotators

    URL

    github.com/markedjs/marked/discussions/1202
  5. Oct 2020
  6. github.com github.com
    Constants in markup by Rich-Harris · Pull Request #33 · sveltejs/rfcs
    1
    1. TylerRick 13 Oct 2020
      but this RFC addresses a significant pain point I've had with {#each} blocks doing data visualization and graphics.
      pain point especially visualization use cases
    Visit annotations in context

    Tags

    Annotators

    URL

    github.com/sveltejs/rfcs/pull/33