rangesBuffer.writeByte('-'.code)
          rangesBuffer.writeByte('-'.code)
        }
        is MappedRange.Inline1 -> {
          rangesBuffer.writeByte(range.b1)
          rangesBuffer.writeByte(range.b2)
          rangesBuffer.writeByte('-'.code)
        }
        is MappedRange.Inline2 -> {
          rangesBuffer.writeByte(range.b1)
          rangesBuffer.writeByte(range.b2)
          rangesBuffer.writeByte(range.b3)

        }
  }

  data class Inline1(
    override val rangeStart: Int,
    private val mappedTo: ByteString,
  ) : MappedRange {
    val b1: Int
      get() {
        val b3bit8 = mappedTo[0] and 0x80 != 0
        return if (b3bit8) 123 else 122
      }

    val b2: Int
      get() = mappedTo[0] and 0x7f
  }

  data class Inline2(
    override val rangeStart: Int,

+++ /dt9/usr/include/x86_64-linux-gnu/sys/cdefs.new.h   2022-11-04 17:17:31.727061220 +0000
@@ -320,7 +320,7 @@

 /* GCC 4.3 and above with -std=c99 or -std=gnu99 implements ISO C99
    inline semantics, unless -fgnu89-inline is used.  */
-#if (!defined __cplusplus || __GNUC_PREREQ (4,3)) && defined __GNUC__
+#if (!defined __cplusplus || __GNUC_PREREQ (4,3) || defined __clang__) && defined __GNUC__

	"fmt"
	"slices"

	"github.com/tinylib/msgp/msgp"
)

// xlMetaInlineData is serialized data in [string][]byte pairs.
type xlMetaInlineData []byte

// xlMetaInlineDataVer indicates the version of the inline data structure.
const xlMetaInlineDataVer = 1

// versionOK returns whether the version is ok.
func (x xlMetaInlineData) versionOK() bool {
	if len(x) == 0 {
		return true
	}

import org.eclipse.aether.artifact.Artifact;
import org.eclipse.aether.deployment.DeployRequest;
import org.eclipse.aether.installation.InstallRequest;

import static java.util.Objects.requireNonNull;

/**
 * Inliner POM transformer. The goal of this transformer is to fix Maven 3 issue about emitting (installing, deploying)
 * unusable POMs when using CI Friendly Versions.
 *
 * @since TBD
 */
@Singleton
@Named

			metaArr[index].ModTime = modTime
			metaArr[index].VersionID = versionID
			if !metaArr[index].InlineData() {
				// If the data is not inlined, we may end up incorrectly
				// inlining the data here, that leads to an inconsistent
				// situation where some objects are were not inlined
				// were now inlined, make sure to `nil` the Data such
				// that xl.meta is written as expected.
				metaArr[index].Data = nil
			}

	return ok
}

// InlineData returns true if object contents are inlined alongside its metadata.
func (fi FileInfo) InlineData() bool {
	_, ok := fi.Metadata[ReservedMetadataPrefixLower+"inline-data"]
	// Earlier MinIO versions didn't reset "x-minio-internal-inline-data"
	// from fi.Metadata when the object was tiered. So, tiered objects

# Online help key for log.
online.help.name.log=log
# Online help key for general settings.
online.help.name.general=general
# Online help key for role.
online.help.name.role=role
# Online help key for job log.
online.help.name.joblog=joblog
# Online help key for keymatch.
online.help.name.keymatch=keymatch
# Online help key for related query.
online.help.name.relatedquery=relatedquery

1 disk2/testbucket/file/xl.meta XL2 Æ X ¨Versions‘‚¤Type ¥V2ObjÞ ¢IDÄ ¤DDirÄ Ÿl;âF?Gq¦Ç ºª?ò¦EcAlgo £EcM £EcN §EcBSizeÒ §EcIndex ¦EcDist” ¨CSumAlgo ¨PartNums‘ ©PartETags‘ ©PartSizes‘Ò ªPartASizes‘Ò ¤SizeÒ ¥MTimeÓ ð ÞÍ &˜§MetaSys ¼x-minio-internal-inline-dataÄ true§MetaUsr‚¤etagÙ fffb6377948ebea75ad2¬content-type¸application/octet-streamÎ7£ï; disk1/testbucket/file/xl.meta 䱘′ ÆĀ腘嚨牥楳湯酳ꒂ祔数ꔁ㉖扏 ᄀ䦢쑄 ꐀ䑄物Ⴤ沟㽆煇잦Вꪺ䖦䅣杬ů䖣䵣ꌂ捅Ɏ䖧䉣楓敺Ò ꜀捅湉敤ɸ䖦䑣獩鑴̂Ą䎨畓䅭杬ů储牡乴浵酳꤁慐瑲呅条酳ꦠ慐瑲楓敺酳ÒЂꨀ慐瑲十穩獥튑Ȁ 厤穩퉥Ȁ 䶥楔敭ᛓ翰췞☝Ꞙ敍慴祓腳碼洭湩潩椭瑮牥慮⵬湩楬敮搭瑡쑡琄...

<img src="/img/tutorial/generate-clients/image08.png">

## Benefits { #benefits }

When using the automatically generated clients, you would get **autocompletion** for:

* Methods.
* Request payloads in the body, query parameters, etc.
* Response payloads.

You would also have **inline errors** for everything.