bitproto v1.2.0

Changes:

• LSP Server: Add a simple bitproto-language-server, tested on neovim and vscode.
• VsCode Extension: Upgraded to support bitproto-language-server (v1.2.0)

Upgraded:

• bitproto compiler → v1.2.0 (to support lsp feature)
• bitproto-language-server → v1.2.2 (https://pypi.org/project/bitproto-language-server/)
• vscode extension → v1.2.0 (https://marketplace.visualstudio.com/items?itemName=hit9.bitproto)

No changes for C/Python/Go lib.

How to Install:

• https://github.com/hit9/bitproto/tree/master/editors/language_server
• Vscode: https://github.com/hit9/bitproto/tree/master/editors/vscode/bitproto

bitproto v1.1.2

Changes:

• Feature: Allow using constants as option values #63 #61

Upgraded: bitproto compiler → v1.1.2

How to upgrade: pip install bitproto -U

No changes for C/Python/Go lib.

bitproto v1.1.1

Changes:

• Fix bug: enum (importing from other bitproto)'s field name generation bug. #53 #52
• Fix bug: import statements of bitproto should be placed ahead of other declarations. #53

Upgraded:

bitproto compiler → v1.1.1

No changes for C/Python/Go lib.

bitproto v1.1.0

Changes v1.1.0:

PR: #48

• Improve C bitprotolib performance BpCopyBufferBits
• Fix bitproto compiler python error for __post_init__ function
• Improve C bitprotolib performance array of byte; uint8/16/32/64; int8/16/32/64 and enum, alias of them

Upgraded:

• bitproto compiler → v1.1.0
• bitproto c lib → v1.1.0

bitproto v1.0.1

PyPI: https://pypi.org/project/bitproto/1.0.1

Changes:

• Add support for Python 3.11.1

bitproto v1.0.0

PyPI: https://pypi.org/project/bitproto/1.0.0/

Changes:

• First fully release version

bitproto v0.4.6

PyPI: https://pypi.org/project/bitproto/0.4.6/

Changes:

• Support signed integers with arbitrary bits, e.g. int24

https://bitproto.readthedocs.io/en/latest/changelog.html#version-0-4-6

bitproto v0.4.5

https://pypi.org/project/bitproto/0.4.5/

changes: https://bitproto.readthedocs.io/en/latest/changelog.html#version-0-4-5

bitproto v0.4.4

• Fix setup issue.

bitproto v0.4.2

• Allow using type as message field name, fixes issue #39.