Raphael
> As for the rendered documentation, the simplest would be to consider them implicit and not list them in the documentation. How many entries for == do we really want...
Arguably, neither Quick Help nor Playgrounds have quite the same set of requirements as (persistent) HTML documentation. Maybe Jazzy should -- carefully! -- clarify diverging requirements and implement accordingly. As...
> If Jazzy were to add support for additional callouts with the traditional syntax pattern, Xcode would interpret them as unordered lists instead. I think that's a fair compromise. No...
I'm fine with "show as much as possible" for internal developer doc. But shipping a closed-source product causes different needs. While I don't imagine I can really hide stuff from...
I don't think I want symbols in `#if DEBUG ... #endif` in customer-facing documentation.
I have a similar issue. ```kotlin verify(someBean).genericMethod(org.mockito.ArgumentMatchers.any()) // --> compiles verify(someBean).genericMethod(com.nhaarman.mockitokotlin2.any()) // --> Type inference failed: Not enough information to infer parameter T ``` Comparing the type signatures: ```java public...
I don't have access anymore to the codebase I observed this in. Now (Kotlin 1.3.40) I have trouble reproducing. ```kotlin import com.nhaarman.mockitokotlin2.any import com.nhaarman.mockitokotlin2.doReturn import com.nhaarman.mockitokotlin2.mock import com.nhaarman.mockitokotlin2.verify import org.junit.Test...
FWIW, I think [ewels/rich-click](https://github.com/ewels/rich-click) implements something similar as well.
Can't speak for @mikefarah , but it seems to that issues with installing yq from a 3rd-party PPA in WSL is _mildly_ out of scope here. FWIW, here's how I...
Use Case: Photo collection in a company. - Employees must be able to opt-in/-out of certain usages of photos they are in. - Employees should be able to call attention...