Re:Stable Diffusion 2.0 and the Importance of Negative Promp...
by _aavaa_ on Monday November 28, 2022 @09:35PM
(#33782997)
// The preceding line is lying.
Re:Stable Diffusion 2.0 and the Importance of Negative Promp...
by taneq on Tuesday November 29, 2022 @02:46AM
(#33784744)
Seems a bit rough to try and make it go back in time! ;)
Re:Stable Diffusion 2.0 and the Importance of Negative Promp...
by _aavaa_ on Wednesday November 30, 2022 @01:44PM
(#33805528)
Not at all. The text file has no idea of time, it all exists at once.
Re:Stable Diffusion 2.0 and the Importance of Negative Promp...
by johnfn on Monday November 28, 2022 @09:48PM
(#33783086)
I had an experience once where copilot generated some code with a bug in it, so I wrote a comment to the effect of
// this fixes [the bug in the previous code]
and it worked. :)
Re:Stable Diffusion 2.0 and the Importance of Negative Promp...
by arthurcolle on Thursday December 01, 2022 @04:42PM
(#33823262)
This is pretty funny
Re:Stable Diffusion 2.0 and the Importance of Negative Promp...
by function_seven on Tuesday November 29, 2022 @01:13AM
(#33784227)
I’m going to try
// This method will determine if input program halts or loops
I’ll reply here once I have the code generated.
Re:Stable Diffusion 2.0 and the Importance of Negative Promp...
by pavlov on Tuesday November 29, 2022 @01:40AM
(#33784387)
//FIXME as a negative prompt might be the code equivalent of “poorly drawn face”.
Re:Stable Diffusion 2.0 and the Importance of Negative Promp...
by taneq on Tuesday November 29, 2022 @01:56AM
(#33784478)
Probably //HACK and //WTF too ;)
Re:Stable Diffusion 2.0 and the Importance of Negative Promp...
by Eleison23 on Tuesday November 29, 2022 @02:40PM
(#33792211)
In the TinyMUD world, one of our most esteemed client hackers became renowned for writing the comment in his code:
/* drunk, fix later */
Re:Stable Diffusion 2.0 and the Importance of Negative Promp...
by riversflow on Tuesday November 29, 2022 @02:11AM
(#33784557)
Is copilot also trained on pull request comments?
Might try: // lgtm!
// The following code does not contain any bugs:
<tab>