Skip to main content
"his/her" pls what year is it
Source Link
thejonymyster
  • 2.4k
  • 6
  • 13

Posting a code snippet instead of a complete answer

Note: There is now a separate question covering this loophole in more detail.

This is a issue mainly for , and variants.

Only in very few cases this seriously affects .

The issue is when someone post a function, a method, an instruction or a code-snippet instead of a complete program. And then score his/hertheir answer based on only what was posted. This gives an unfair advantage over who posted a complete solution.

Here is an example of a complete C Hello World program in 53 bytes:

#include<stdio.h>
int main(){printf("Hello World!");}

But, the answerer, with the intent to defeat another answer in code-golf, posts this instead, claiming that his/hertheir answer is 22 bytes:

printf("Hello World!")

Posting a code snippet instead of a complete answer

Note: There is now a separate question covering this loophole in more detail.

This is a issue mainly for , and variants.

Only in very few cases this seriously affects .

The issue is when someone post a function, a method, an instruction or a code-snippet instead of a complete program. And then score his/her answer based on only what was posted. This gives an unfair advantage over who posted a complete solution.

Here is an example of a complete C Hello World program in 53 bytes:

#include<stdio.h>
int main(){printf("Hello World!");}

But, the answerer, with the intent to defeat another answer in code-golf, posts this instead, claiming that his/her answer is 22 bytes:

printf("Hello World!")

Posting a code snippet instead of a complete answer

Note: There is now a separate question covering this loophole in more detail.

This is a issue mainly for , and variants.

Only in very few cases this seriously affects .

The issue is when someone post a function, a method, an instruction or a code-snippet instead of a complete program. And then score their answer based on only what was posted. This gives an unfair advantage over who posted a complete solution.

Here is an example of a complete C Hello World program in 53 bytes:

#include<stdio.h>
int main(){printf("Hello World!");}

But, the answerer, with the intent to defeat another answer in code-golf, posts this instead, claiming that their answer is 22 bytes:

printf("Hello World!")
Remove gendered language
Source Link

Posting a code snippet instead of a complete answer

Note: There is now a separate question covering this loophole in more detail.

This is a issue mainly for , and variants.

Only in very few cases this seriously affects .

The issue is when someone post a function, a method, an instruction or a code-snippet instead of a complete program. And then score his/her answer based on only what was posted. This gives an unfair advantage over who posted a complete solution.

Here is an example of a complete C Hello World program in 53 bytes:

#include<stdio.h>
int main(){printf("Hello World!");}

But, the answerer, with the intent to defeat another answer in code-golf, posts this instead, claiming that his/her answer is 22 bytes:

printf("Hello World!")

Posting a code snippet instead of a complete answer

Note: There is now a separate question covering this loophole in more detail.

This is a issue mainly for , and variants.

Only in very few cases this seriously affects .

The issue is when someone post a function, a method, an instruction or a code-snippet instead of a complete program. And then score his/her answer based on only what was posted. This gives an unfair advantage over who posted a complete solution.

Here is an example of a complete C Hello World program in 53 bytes:

#include<stdio.h>
int main(){printf("Hello World!");}

But, the answerer, with the intent to defeat another answer in code-golf, posts this instead, claiming that his answer is 22 bytes:

printf("Hello World!")

Posting a code snippet instead of a complete answer

Note: There is now a separate question covering this loophole in more detail.

This is a issue mainly for , and variants.

Only in very few cases this seriously affects .

The issue is when someone post a function, a method, an instruction or a code-snippet instead of a complete program. And then score his/her answer based on only what was posted. This gives an unfair advantage over who posted a complete solution.

Here is an example of a complete C Hello World program in 53 bytes:

#include<stdio.h>
int main(){printf("Hello World!");}

But, the answerer, with the intent to defeat another answer in code-golf, posts this instead, claiming that his/her answer is 22 bytes:

printf("Hello World!")
link to the expanded version of the loophole
Source Link
user62131
user62131

Posting a code snippet instead of a complete answer

Note: There is now a separate question covering this loophole in more detail.

This is a issue mainly for , and variants.

Only in very few cases this seriously affects .

The issue is when someone post a function, a method, an instruction or a code-snippet instead of a complete program. And then score his/her answer based on only what was posted. This gives an unfair advantage over who posted a complete solution.

Here is an example of a complete C Hello World program in 53 bytes:

#include<stdio.h>
int main(){printf("Hello World!");}

But, the answerer, with the intent to defeat another answer in code-golf, posts this instead, claiming that his answer is 22 bytes:

printf("Hello World!")

Posting a code snippet instead of a complete answer

This is a issue mainly for , and variants.

Only in very few cases this seriously affects .

The issue is when someone post a function, a method, an instruction or a code-snippet instead of a complete program. And then score his/her answer based on only what was posted. This gives an unfair advantage over who posted a complete solution.

Here is an example of a complete C Hello World program in 53 bytes:

#include<stdio.h>
int main(){printf("Hello World!");}

But, the answerer, with the intent to defeat another answer in code-golf, posts this instead, claiming that his answer is 22 bytes:

printf("Hello World!")

Posting a code snippet instead of a complete answer

Note: There is now a separate question covering this loophole in more detail.

This is a issue mainly for , and variants.

Only in very few cases this seriously affects .

The issue is when someone post a function, a method, an instruction or a code-snippet instead of a complete program. And then score his/her answer based on only what was posted. This gives an unfair advantage over who posted a complete solution.

Here is an example of a complete C Hello World program in 53 bytes:

#include<stdio.h>
int main(){printf("Hello World!");}

But, the answerer, with the intent to defeat another answer in code-golf, posts this instead, claiming that his answer is 22 bytes:

printf("Hello World!")
edited body
Source Link
Timwi
  • 12.9k
  • 1
  • 20
  • 23
Loading
Post Made Community Wiki by C. K. YoungMod
Example
Source Link
Victor Stafusa
  • 8.8k
  • 1
  • 15
  • 21
Loading
Source Link
Victor Stafusa
  • 8.8k
  • 1
  • 15
  • 21
Loading