protocolbuffers / protocolbuffers/protobuf

Warning in repeated_ptr_field.h about conversion from `size_t` to `int` causes compiler error

Open
#23,248 1 comment 0 reactions 1 assignee View on GitHub

@anandolee is already working on this.

Since Sep 12, 2025.

help wanted
Dominant language
C++
Stars
72k
Forks
16.3k
Avg merge
1d 17h
Merged PRs (30d)
140

Description

What version of protobuf and what language are you using?
Version: main/v6.30.1
Language: C++

What operating system (Linux, Windows, ...) and version?

Windows

What runtime / compiler are you using (e.g., python version or gcc version)

MSVC 17.12.5

What did you do?
I am compiling code that includes a generated .pb.h file.

What did you expect to see
What did you see instead?

I am running into compiler warnings, which are treated as errors:

C:\dev\conan-cache\p\protoee6b55d34d238\p\include\google/protobuf/repeated_ptr_field.h(1575): error C2220: the following warning is treated as an error
C:\dev\conan-cache\p\protoee6b55d34d238\p\include\google/protobuf/repeated_ptr_field.h(1575): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data
C:\dev\conan-cache\p\protoee6b55d34d238\p\include\google/protobuf/repeated_ptr_field.h(1580): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data
C:\dev\conan-cache\p\protoee6b55d34d238\p\include\google/protobuf/repeated_ptr_field.h(1584): warning C4267: 'argument': conversion from 'size_t' to 'int', possible loss of data
C:\dev\conan-cache\p\protoee6b55d34d238\p\include\google/protobuf/repeated_field.h(145): warning C4267: 'argument': conversion from 'size_t' to 'const _Ty', possible loss of data

I believe that this issue still exists in the codebase:

Anything else we should know about your project / environment

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.